search for: e2fsck'ing

...rted which clearly shows that there's a "\n" missing in the printk in ~/include/linux/ext3_jbd.h, line 97. (or the string printed misses one, don't know). ext3 remounted the drive readonly; I did a badblock test on it (which returned zero errors, *sigh*, I love flaky hardware), e2fsck'ed it (complained only about a missing lost+found an some wrong free block counts, nothing major), and then tried to remount it rw again but got the following error: root@yadda:~# mount -oremount,rw /dev/hdk1 mount: block device /dev/hdk1 is write-protected, mounting read-only root@yadda:~# w...

...ad to power cycle it (buggy VM.. grumble :-) and now I cannot get my filesystem back. It is only a test filesystem so I don't need the data. But I want this to work before I put real data on it. If I "fsck /dev/md1", it says Parallelizing fsck version 1.22 (22-Jun-2001) e2fsck 1.22, 22-Jun-2001 for EXT2 FS 0.5b, 95/08/09 Superblock has external ext3 journal device (unsupported). Abort<y>? So I say yes. I try to mount it : mount /dev/md1 /export/eno/1 -t ext3 and the kernel log says: EXT3-fs: External journal has more than one user (unsupporte...