On Feb 06, 2009 13:23 +0100, J.D. Bakker wrote: > At 23:29 -0700 05-02-2009, Andreas Dilger wrote: >> On Feb 06, 2009 04:06 +0100, J.D. Bakker wrote: >> > On reboot the system refused to auto-fsck /dev/md0. A manual e2fsck -nv >> > /dev/md0 reported: >> > [...] >> > Error writing block 1 (Attempt to write block from filesystem resulted >>> in short write). Ignore error? no >>> Error writing block 2 (Attempt to write block from filesystem resulted >>> in short write). Ignore error? no >>> Error writing block 3 (Attempt to write block from filesystem resulted >>> in short write). Ignore error? no >> >> This is a serious problem. > > Could this be caused by my using the -n option on e2fsck (see my reply to > Eric)? Then it is a bug in e2fsck. e2fsck shouldn't even TRY to write to the filesystem without asking the user first, and "-n" means the answer is always no so it should never do this. >> > As I said, is there anything I can do to recover my data, or to make >> >>> sure this doesn't happen again? >> >> I would say to run "e2fsck -fp /dev/XXX" and your data _should_ be >> there. > > No dice: > > newraidfs: Note: if several inode or block bitmap blocks or part > of the inode table require relocation, you may wish to try > running e2fsck with the '-b 32768' option first. The problem > may lie only with the primary block group descriptors, and > the backup block group descriptors may be OK. > > newraidfs: Block bitmap for group 7808 is not in group. (block 3731742663) > > newraidfs: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. > (i.e., without -a or -p options) Then you should run it with "-f" and maybe "-b32768" (if it doesn't do this on its own). If you want to avoid hitting "y" 27000 times, you should also add "-y". Cheers, Andreas -- Andreas Dilger Sr. Staff Engineer, Lustre Group Sun Microsystems of Canada, Inc. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
