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

Re: files disappear in ext3 filesystem



Thank you first
My English is bad to make clear

There are three boxes install RH7.2(kernel 2.4.7-10) say mikelee,
peanut, afssvr

after power fail,

only one, mikelee seem to be working right

two fail boxes 
(one, peanut already reinstall because many people depend on it, 
and one, afssvr still here and fail to restart)

mikelee log
------------------------------------------------------------------------------------

Jan 14 09:02:52 mikelee fsck: /: |                                                                 
Jan 14 09:02:52 mikelee last message repeated 2 times
Jan 14 09:02:52 mikelee fsck: Inode 917997, i_blocks is 64, should be 16.  FIXED. 
Jan 14 09:02:52 mikelee fsck: /: Inode 917999, i_blocks is 64, should be 16.  FIXED. 
Jan 14 09:02:52 mikelee fsck: Inode 1163457, i_blocks is 64, should be 8.  FIXED. 
Jan 14 09:02:52 mikelee fsck: Inode 1819135, i_blocks is 72, should be 16.  FIXED. 
Jan 14 09:02:52 mikelee fsck: /:  
Jan 14 09:02:52 mikelee fsck: Inode 1819134, i_blocks is 584, should be 560.  FIXED. 
Jan 14 09:02:52 mikelee fsck: Inode 2212215, i_blocks is 64, should be 8.  FIXED. 
Jan 14 09:02:52 mikelee fsck: /:  
Jan 14 09:02:52 mikelee fsck: Inode 2212254, i_blocks is 200, should be 160.  FIXED. 
Jan 14 09:02:52 mikelee fsck: /:  
Jan 14 09:02:52 mikelee fsck: Inode 2277889, i_blocks is 816, should be 776.  FIXED. 
Jan 14 09:02:52 mikelee fsck: /: Inode 2277887, i_blocks is 408, should be 352.  FIXED. 
Jan 14 09:02:52 mikelee fsck: /: Inode 2277888, i_blocks is 328, should be 304.  FIXED. 
Jan 14 09:02:52 mikelee fsck: /: Inode 2277893, i_blocks is 184, should be 160.  FIXED. 
Jan 14 09:02:52 mikelee fsck: /: Inode 2277894, i_blocks is 632, should be 608.  FIXED. 
Jan 14 09:02:52 mikelee fsck: /: Inode 2277892, i_blocks is 1304, should be 1296.  FIXED. 
Jan 14 09:02:52 mikelee fsck: /: Inode 2277886, i_blocks is 1624, should be 1584.  FIXED. 
Jan 14 09:02:52 mikelee fsck: /: Inode 2277895, i_blocks is 176, should be 152.  FIXED. 
Jan 14 09:02:52 mikelee fsck: /:  
Jan 14 09:02:52 mikelee fsck: Inode 2277890, i_blocks is 512, should be 472.  FIXED. 
Jan 14 09:02:52 mikelee fsck: /:  
Jan 14 09:02:52 mikelee fsck: Inode 4964530, i_blocks is 80, should be 72.  FIXED. 
Jan 14 09:03:05 mikelee named[707]: starting BIND 9.1.3 -u named
Jan 14 09:02:52 mikelee fsck: /:  
Jan 14 09:02:52 mikelee fsck: Inode 4964529, i_blocks is 920, should be 896.  FIXED. 
Jan 14 09:02:52 mikelee fsck: Inode 5636373, i_blocks is 64, should be 8.  FIXED. 
Jan 14 09:02:52 mikelee fsck: Inode 6734006, i_blocks is 64, should be 48.  FIXED. 
Jan 14 09:03:05 mikelee named[707]: using 1 CPU
Jan 14 09:02:52 mikelee fsck: /:  
Jan 14 09:02:52 mikelee fsck: Inode 6734038, i_blocks is 232, should be 176.  FIXED. 
Jan 14 09:02:52 mikelee fsck: /: Inode 6734015, i_blocks is 1000, should be 944.  FIXED. 
Jan 14 09:02:52 mikelee fsck: /: 223250/7028736 files (1.5% non-contiguous), 3783967/14056867 blocks
------------------------------------------------------------------------------------


peanut log:
------------------------------------------------------------------------------------
Jan 14 09:22:33 peanut fsck: / was not cleanly unmounted, check forced. 
Jan 14 09:22:46 peanut automount[682]: parse(sun): unknown option: -nobrowse
Jan 14 09:22:33 peanut fsck: /: |                                                                 
Jan 14 09:22:33 peanut fsck: /: |                                                                 
Jan 14 09:22:33 peanut fsck: Inode 2408738, i_blocks is 64, should be 8.  FIXED. 
Jan 14 09:22:33 peanut fsck: Inode 5144818, i_blocks is 64, should be 8.  FIXED. 
Jan 14 09:22:33 peanut fsck: /: Inode 5144819, i_blocks is 64, should be 8.  FIXED. 
Jan 14 09:22:33 peanut fsck: /: Inode 5144820, i_blocks is 64, should be 8.  FIXED. 
Jan 14 09:22:33 peanut fsck: Deleted inode 6242432 has zero dtime.  FIXED. 
Jan 14 09:22:46 peanut automount[682]: using kernel protocol version 3
Jan 14 09:22:33 peanut fsck: Inode 7078080, i_blocks is 96, should be 80.  FIXED. 
Jan 14 09:22:33 peanut fsck: /: 143780/7241728 files (1.1% non-contiguous), 986610/14458492 blocks 
------------------------------------------------------------------------------------

afssvr can not start because some file can not be read
using RH7.2 cd and choose linux rescue option and disable several can not start services
use fsck manual it seem to be ok and pass
now it can start with many many files can not access, for examples use mc to view or edit a file 
the tty is dead
nothing in lost+found




Theodore Tso wrote:

>On Thu, Jan 17, 2002 at 05:08:16PM +0800, Mike Lee wrote:
>
>>I met a power fail
>>all sub-folders an files in /home folder are disappear.
>>and fsck continue to report error in the filesystem.
>>
>
>Can you send us the errors which fsck and/or the kernel reported?
>What version of the kernel were you using?  What version of
>e2fsck/e2fsprogs were you using?  What kind of hardware are we dealing
>with?
>
>You might also want to check /var/log/messages to see if there were
>any messages from the disk drive indicating hardware errors (i.e., bad
>blocks on the disk drive).
>
>>however, I can see any files and folder in debugfs and can rdump them to
>>another folder and format ... and reinstall
>>so bad!!!
>>
>>Question:
>>Can I have a simple way to recover the data without reinstall and format
>>
>
>Normally this isn't a problem; you should needed to do so.  But your
>bug report / question is roughly equivalent to complaining to a car
>company that "my car stopped working, and the only way I could fix it
>was to take it to a smelter, melt it down into scrap heap, and then
>reconstitute the car from the resulting metal slag.  This is so bad!
>Can you tell me how to fix it in the future?"
>
>And you don't tell the car company any symptoms before you destroyed
>it, and you don't even allow the company to look at the malfunctioning
>car (since you've already melted it down into scrap metal) when you
>complain.  Heck, you don't even bother to tell the car company what
>the model or year of the car --- they should be able to figure that
>out by mind-reading.
>
>For future reference....  the e2fsck page has a section on "reporting
>bugs".  This is also useful steps if you're not sure whether you're
>dealing with a bug, user error, or hardware error.  Something else
>which is useful if you have a fairly recent version of e2fsprogs, is
>to use the "e2image -r" command (read the man page for more details),
>and make provisions to send me the raw metadata image dump so I can
>investigate what might be going on.
>
>We'd like to help, we really would.... but we need information in
>order to help you.  At the very least, please don't destroy the
>filesystem until you give us a chance to tell you what kind of
>information would be most helpful in trying to help track down the bug
>(if bug it be) or cause of your difficulties.
>
>						- Ted
>
>
>
>_______________________________________________
>Ext3-users mailing list
>Ext3-users redhat com
>https://listman.redhat.com/mailman/listinfo/ext3-users
>

-- 

Mike Lee mike li bamboonetworks com <mailto:mike li bamboonetworks com>
room 1122-1123 international bank tower
191 dong feng rd west guangzhou, p.r.c.
t) 8620-8135 1210 ext. 58
f) 8620-8135 1207

</temp/mailfoot/logo.gif> <http://www.bamboonetworks.com>

 hong kong                         guangzhou                         seoul                   tokyo



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