From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Raskin Subject: Re: cleanup after a small data loss on incorrect shutdown. Date: Fri, 12 Jun 2009 15:56:01 +0400 Message-ID: <4A324251.1060207@rambler.ru> References: <4A30FC2E.3030804@rambler.ru> <20090612105332.GG3834@think> <4A32374A.6080900@rambler.ru> <20090612114230.GH3834@think> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 To: Chris Mason , Michael Raskin , linux-btrfs@vger.kernel.org Return-path: In-Reply-To: <20090612114230.GH3834@think> List-ID: Chris Mason wrote: >>> I'd say to send us the btrfsck output, it will help answer these >>> questions. >> Oh, easily. "Bad block ". > > Btrfs deals in byte numbers not block numbers ;) Interesting to know. Maybe just adding "at" in the message would reduce confusion. It doesn't look like it is a canonical bad block anyway. >> That's all. Reading one of the damaged file actually returned >> "Input/output error" - probably it tried to read beyond end-of-device. I >> had to kill this file (practical testing means that to continue to use >> my notebook normally I had to nuke the damaged file and get intact >> copies). The "no such file except in readdir" is still there right now. > > Ok, btrfsck will give us more output when it finishes, but it hasn't > finished. It would help to use btrfs-image to send us a coyp of the > metadata so we can fix the btrfsck bug. Well, as the partition fills up at ~25 G of 30 G used, I guess that average metadata size is >=1G for that partition. And now I destroyed the evidence to make the notebook boot. The disappearing file, though, is a minor annoyance so I can keep it and do whatever is needed with btrfs-image..