On Wed, Apr 20, 2016 at 1:09 PM, Weiner, Michael <weinerm(a)ccf.org> wrote:
From: chris(a)colorremedies.com [mailto:chris@colorremedies.com] On
Behalf Of Chris Murphy
On Wed, Apr 20, 2016 at 12:58 PM, Weiner, Michael <weinerm(a)ccf.org> wrote:
> From: chris(a)colorremedies.com [mailto:chris@colorremedies.com] On
> Behalf Of Chris Murphy
>
> On Wed, Apr 20, 2016 at 12:50 PM, Weiner, Michael <weinerm(a)ccf.org> wrote:
>
>>> Because I believe that I built the 15Tb filesystem for ext3 using 8K
>>> blocks when I set this up several years back
>
>> What platform was it created on and has been used on until now?
>
> CentOS 5.10 and yes, it was in use earlier in the day :(
It's probably a 4K blocksize if this was created on x86 (including x86_64). I'm
not sure what the cutoff was for 1K blocksizes and ext3, I've definitely seen 1K
blocksizes used for 250MB boot volumes from that epoch. But 1K blocksize for 15TB? Anyway
that's pretty incredible to have a 15TB ext3 file system running on CentOS 5. I
didn't know that was even possible. That size filesystem in that era was definitely
XFS territory.
>
>> At least XFS, ext4, and Btrfs right now can't mount file systems with blocks
larger than the pagesize, and on x86 Linux pagesize is 4K.
>
> I thought 16Tb was the max ext3 that could be handled
The size of the filesystem is not what I'm talking about. An 8K blocksize is valid
for filesystem creation but invalid for mounting on
x86 32 or 64 bit. So if you're doing all of this on x86, it's not an 8KB
blocksize. It's 4K or less.
But then the eftools complain and don’t work properly, example
[root@raos_apps01 ~]# mke2fs -n /dev/sdb1
mke2fs 1.39 (29-May-2006)
There's the problem. Why are you using such an ancient mkfs? That
version doesn't support big file systems. When I use this same command
on Fedora 23 which has 1.42.13, it works fine for ext2, ext3 and ext4
on a virtual size 15TB file system and uses 4K block size.
--
Chris Murphy