Date: Tue, 6 Apr 2004 18:49:53 -0400 From: "Will Saxon" <WillS@housing.ufl.edu> To: <current@freebsd.org> Subject: drive failure, now 'cannot alloc 494581644 bytes for inoinfo' and 'bad inode number 3556352 to nextinode' Message-ID: <0E972CEE334BFE4291CD07E056C76ED8CBBEE3@bragi.housing.ufl.edu>
next in thread | raw e-mail | index | archive | help
Hello, Today, I had a drive fail in a large raid 5 array hosted off of a ciss = device. I removed the bad drive but before I was able to get another = drive swapped in, another drive seemed to just lose power and then the = system panicked. =20 I swapped in a spare drive and restarted the system. The controller said = the array was 'ok' and would recover. However, FreeBSD is having a hard = time fsck'ing the partition. At the time of the crash, I was using FreeBSD 5.2.1-RC2, however I have = since updated to 5.2.1-RELEASE-p4. The array has 1 partition and 2 = slices - one 4GB swap slice and 1 400+GB storage slice. This was being = used in a samba pilot and had the softupdates, suiddir, noexec, nodev = and acl options enabled. Basically, in phase 1 fsck -y complains that it cannot allocate enough = bytes for inoinfo, then there are a bunch of the following: UNKNOWN FILE TYPE I=3D####### UNEXPECTED SOFT UPDATE INCONSISTENCY then finally: fsck_4.2bsd: bad inode number 3556352 to nextinode Any ideas? -Will _____________________________________________ Will Saxon Systems Programmer - Network Services Department of Housing and Residence Education University of Florida Email: wills@housing.ufl.edu Phone: (352) 392-2171 x10148
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0E972CEE334BFE4291CD07E056C76ED8CBBEE3>