Messages in this thread | | | Date | Wed, 27 Oct 1999 23:25:49 +0200 | From | Marc Mutz <> | Subject | Re: 2.2.13 ext2 errors |
| |
Jeff Garzik wrote: > > I got a bunch of these last night on an unpatched copy of 2.2.13. > Something similar with my box, too.
> Several CVS copies, an egcs build, and 'bzcat|tar xf-' were all running > in the background, so the single 4GB disk was getting hit pretty hard, > in addition to NFS and knfsd. Hardware is K6 350, > K6-2-300, no NFS (neither k- nor userland), but restoring the content of my blowfish-encrypted loop device with tar at that time.
<snip error msgs>
Oct 27 00:11:32 adam kernel: EXT2-fs error (device loop(7,0)): ext2_check_descriptors: Block bitmap for group 128 not in group (block 1048576)! Oct 27 00:13:27 adam kernel: <dto.> Oct 27 00:47:16 adam kernel: EXT2-fs error (device loop(7,0)): ext2_check_descriptors: Block bitmap for group 10 not in group (block 0)! Oct 27 00:47:33 adam kernel: <dto.> Oct 27 00:47:45 adam kernel: <dto.> Oct 27 00:47:56 adam kernel: <dto.>
Never had this with 2.2.12 (current /var/log/messages goes back to 8-sep-99, archived version back to 10-mar-99 with no such message), although I use my crypto-loop-device daily (contains my mail folder).
I changed the following variables yesterday night:
1.) Updated (2.2.12 with international kernel patch) to (2.2.13 with additional raid0145 from 24-08-1999 for 2.2.11) 2.) Made the transition from mdtools-0.42 to raidtools-0.90 (24-08-1999 snapshot) 3.) re-made my raid-array thus: # cat /proc/mdstat Personalities : [raid0] [raid5] read_ahead 1024 sectors md1 : active raid0 sdc5[2] sdb5[1] sda5[0] 3146976 blocks 32k chunks md2 : active raid5 sdc6[2] sdb6[1] sda6[0] 1048832 blocks level 5, 32k chunk, algorithm 2 [3/3] [UUU] md3 : active raid5 sdc7[2] sdb7[1] sda7[0] 524288 blocks level 5, 8k chunk, algorithm 0 [3/3] [UUU] md4 : active raid0 sdc8[2] sdb8[1] sda8[0] 1573248 blocks 8k chunks md5 : active raid5 sdc10[2] sdb10[1] sda10[0] 3828736 blocks level 5, 32k chunk, algorithm 2 [3/3] [UUU] unused devices: <none>
Previously, they were old-style raid0 and linear devices w/o persistent sb's. The file containing the crypted fs resides on /dev/md5 and is currently 1.2Gb. I previously resized the crypted fs multiple times with the ext2resizer, but the current one was created with the size it has now.
Marc
-- Marc Mutz <Marc@Mutz.com> http://marc.mutz.com/ University of Bielefeld, Dep. of Mathematics / Dep. of Physics
PGP-keyID's: 0xd46ce9ab (RSA), 0x7ae55b9e (DSS/DH)
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |