Re: should ext2fs_get_device_size() be returning EFBIG for >8T (or 16T?)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Eric Sandeen wrote:
> I have a bug saying hey, I can't grow my filesystem on a 16T device, and
> it's because really we can only go to (2^32)-1 blocks, not (2^32)...
> 
> I was going to just silently round down by a block, because for example
> LVM makes it *very* easy to make exactly 16T devices; dropping a block
> at mkfs/growfs time seems reasonable to me.
> 
> So that led me to ext2fs_get_device_size, and I see it actually has the
> maximum allowable filesystem size encoded in it, and you get EFBIG if
> it's bigger.

Actually I guess it's looking at the largest number a blk_t can hold,
but I think the same principle applies.  Maybe it's not a big deal today...

-Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Reiser Filesystem Development]     [Ceph FS]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite National Park]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]     [Linux Media]

  Powered by Linux