On Wed, Apr 20, 2016 at 2:25 PM, Chris Murphy <lists(a)colorremedies.com> wrote:
On Wed, Apr 20, 2016 at 2:07 PM, Chris Murphy
<lists(a)colorremedies.com> wrote:
> On Wed, Apr 20, 2016 at 1:29 PM, Chris Murphy <lists(a)colorremedies.com> wrote:
>> On Wed, Apr 20, 2016 at 1:09 PM, Weiner, Michael <weinerm(a)ccf.org> wrote:
>
>>>
>>> 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.
>
>
https://lwn.net/Articles/177820/
>
> I'm not sure which version of e2fsprogs got this patch, but it seems
> pretty certain your file system was not created with mke2fs 1.39.
This might be wrong. Try -n -F with this old version and see if it works.
I don't know the consequences of forcing it, but you have what you
have, so you could try it if you're convinced you were using such an
old e2fsprogs.
Related. -j isn't the same as mkfs.ext3 I guess, at least not with
such old progs.
tl;dr, best to use mkfs.ext3, mkfs.ext4, etc