From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Michael Styer" Subject: Re: missing files? Date: Sat, 05 Feb 2005 11:31:09 -0500 Message-ID: <1107621069.13887.214400623@webmail.messagingengine.com> References: <1107318853.18354.214122527@webmail.messagingengine.com> <200502022014.23915.vitaly@namesys.com> <1107376028.24415.214183081@webmail.messagingengine.com> <200502041433.27112.vitaly@namesys.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit list-help: list-unsubscribe: list-post: Errors-To: flx@namesys.com Content-Disposition: inline In-Reply-To: <200502041433.27112.vitaly@namesys.com> List-Id: Content-Type: text/plain; charset="us-ascii" To: Vitaly Fertman Cc: Vladimir Saveliev , reiserfs-list@namesys.com On Fri, 4 Feb 2005, Vitaly Fertman said: > > so what I do not understand is why reiserfsck does not report any > problem to you. Which reiserfsprogs do you have? have you 'umount & > mount ro' or 'remount,ro', btw? reiser4 does not do 'remount,ro' > properly yet. have you run fsck.reiser4 on umounted fs? Hmm. I did 'remount,ro', actually; didn't realize that it wouldn't work with reiser4. I have version 1.0.3 of the Gentoo reiser4progs package; fsck.reiser4, mkfs.reiser4 and debugfs.reiser4 all report version 1.0.3. I concluded that fsck.reiser4 wasn't reporting problems just on the basis of the lack of problems noted in the /var/log/messages output on boot, but I hadn't run it manually. OK. So I killed everything that was keeping /usr busy and unmounted it. I ran debugfs.reiser4 on /dev/hdb1 unmounted. Then I mounted the partition ( 'mount -t reiser 4 -o ro,noatime /dev/hdb1 /usr' ). Now debugfs.reiser4 dies with this output: Fatal: Can't read master super block. Error: Can't open reiser4 on /usr and fsck.reiser4 says this: Fatal: Can't read master superblock. Fatal: Failed to open the reiser4 backup. Fatal: Cannot open the FileSysten on (/usr). 1 fatal corruptions were detected in SuperBlock. Run with --build-sb option to fix them. I have the output of my first debugfs run if that would be helpful. I'll put it up for download on the same IP with the filename of mas.devhdb1_unmounted.bz2. I'm going to reboot so that you can get that file (this is my webserver as well...). Regarding the output of fsck.reiser4, it suggests to run fsck.reiser4 --build-sb. What's that going to do to my filesystem? Am I likely to lose the contents (i.e. is it like reformatting) or will it fix the structure without causing data loss? At the minute it seems I still have access to the filesystem, so I could tar everything up now before rebuilding the superblock if doing so would mean losing that data. Do you have any suggestions or advice as to what I should do from here? Thanks very much for your help; I appreciate your taking the time to help me out with this. Michael PS: I've included the list address again in case this discussion might be helpful to anyone else.