On Feb 27, 2014, at 11:19 AM, Justin Brown <[email protected]> wrote:
> I've a 18 tera hardware raid 5 (areca ARC-1170 w/ 8 3 gig drives) in > need of help. Disk usage (du) shows 13 tera allocated yet strangely > enough df shows approx. 780 gigs are free. It seems, somehow, btrfs > has eaten roughly 4 tera internally. I've run a scrub and a balance > usage=5 with no success, in fact I lost about 20 gigs after the > balance attempt. Some numbers: > > terra:/var/lib/nobody/fs/ubfterra # uname -a > Linux terra 3.12.4-2.44-desktop #1 SMP PREEMPT Mon Dec 9 03:14:51 CST > 2013 i686 i686 i386 GNU/Linux This is on i686? The kernel page cache is limited to 16TB on i686, so effectively your block device is limited to 16TB. While the file system successfully creates, I think it's a bug that the mount -t btrfs command is probably a btrfs bug. The way this works for XFS and ext4 is mount fails. EXT4-fs (sdc): filesystem too large to mount safely on this system XFS (sdc): file system too large to be mounted on this system. If you're on a 32-bit OS, the file system might be toast, I'm not really sure. But I'd immediately stop using it and only use 64-bit OS for file systems of this size. Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
