On 2002.11.04 09:51 chrisl@vmware.com wrote: > On Fri, Nov 01, 2002 at 11:55:01AM +0000, Ian Leonard wrote: > > > > I guess we have build/rebuild a hundred systems or so and this > > has been reported once before. We are at the latter stages of a > > development project so there is lot of abuse going on. I seem > > to be the only one knows about the shutdown command. > > Given that it was a power outage, it is possible that the power > > failed again at a crucial stage. Also, as far as I know it shouldn't > > have run fsck at boot time. > > I already get the "/" and "lost+found" from Ian. > I think this drive have run fsck already. > > [chrisl@chrisl image]$ hexdump -c rootdir > 0000000 002 \0 \0 \0 \f \0 001 002 . \0 \0 \0 002 \0 \0 \0 > 0000010 \f \0 002 002 . . \0 \0 \f \0 \0 \0 350 017 \n 002 > 0000020 l o s t + f o u n d \0 \0 \0 \0 \0 \0 > 0000030 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 > * > 0001000 > > The rootdir seems have been regenerated. The inode of loast+found is 12 > instead of 11. There is no trace of deleted file at all. > > In lost+found. Those "#<inode_number>" file should be generated by > fsck. There is 122 dirs and about 400 files in it. I assume your root > directory is not that big. There is other directory get corrupted. > > Because it is already run fsck. It can't really tell what is it look > like when it power off. > Thanks for looking. It is possible that fsck was run by one of the engineers but it may have been run automatically on reboot. I'll request that should it occure again, the disk is left alone. Do you think that this is an ext3 problem or just one of those things that happen from time to time? -- Ian Leonard eMail: ileonard@ntlworld.com Phone: +44 (0)1865 765273 Please ignore spelling and punctuation - I did. _______________________________________________ Ext3-users@redhat.com https://listman.redhat.com/mailman/listinfo/ext3-users
