Date: Mon, 16 Apr 2007 19:10:07 GMT From: Dan D Niles <dan@more.net> To: freebsd-bugs@FreeBSD.org Subject: Re: bin/111146: fsck fails on 6Tfilesystem Message-ID: <200704161910.l3GJA7Qb082383@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/111146; it has been noted by GNATS. From: Dan D Niles <dan@more.net> To: bug-followup@FreeBSD.org Cc: Harrison Grundy <astrodog@gmail.com>, Jan Srzednicki <w@wrzask.pl> Subject: Re: bin/111146: fsck fails on 6Tfilesystem Date: Mon, 16 Apr 2007 14:08:57 -0500 I attached the failed raid device to a newer server with 8G of RAM. I booted to an amd64 kernel, and set datasize limit to 7G. Resource limits (current): cputime infinity secs filesize infinity kB datasize 7340032 kB stacksize-cur 8192 kB coredumpsize infinity kB memoryuse-cur 8093236 kB memorylocked-cur 1299644 kB maxprocesses 6164 openfiles 12328 sbsize infinity bytes vmemoryuse infinity kB Now when I run fsck I get: ** /dev/da0 ** Last Mounted on /LSO ** Phase 1 - Check Blocks and Sizes fsck_ffs: bad inode number 53321728 to nextinode My theory is that some bits got flipped in the meta-data and cg_initediblk is getting a bad value. The value of 1,572,191,256 that it returns just before it fails is greater than the total number of inodes, which is around 784,218,256. It is distressing that some bits in the meta-data could get flipped during normal usage resulting in an unusable filesystem. I have 19 hours before I need to reformat the array and put it back into production. Is there anything else I should try before then? Thanks, Dan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200704161910.l3GJA7Qb082383>