Re: mkfs.ext2 triggerd RAM corruption

2007-05-07 Thread Bill Davidsen
Jan-Benedict Glaw wrote: On Fri, 2007-05-04 16:59:51 +0200, Bernd Schubert <[EMAIL PROTECTED]> wrote: To see whats going on, I copied the entire / (so the initrd) into a tmpfs root, chrooted into it, also bind mounted the main / into this chroot and compared several times /bin of chroot/bin and

Re: mkfs.ext2 triggerd RAM corruption

2007-05-05 Thread Bernd Schubert
On Sat, May 05, 2007 at 02:57:35PM -0400, Theodore Tso wrote: > On Sat, May 05, 2007 at 03:36:37AM +0200, Bernd Schubert wrote: > > distribution: modified debian sarge, in which aspect is the distribution > > important for this problem? mkfs2.ext2 is supposed to write to /dev/sdaX > > and not /dev/

Re: mkfs.ext2 triggerd RAM corruption

2007-05-05 Thread Bernd Schubert
On Sat, May 05, 2007 at 09:12:02PM +0200, Jan Engelhardt wrote: > > On May 5 2007 14:57, Theodore Tso wrote: > >On Sat, May 05, 2007 at 03:36:37AM +0200, Bernd Schubert wrote: > >> distribution: modified debian sarge, in which aspect is the distribution > >> important for this problem? mkfs2.ext2

Re: mkfs.ext2 triggerd RAM corruption

2007-05-05 Thread Jan Engelhardt
On May 5 2007 14:57, Theodore Tso wrote: >On Sat, May 05, 2007 at 03:36:37AM +0200, Bernd Schubert wrote: >> distribution: modified debian sarge, in which aspect is the distribution >> important for this problem? mkfs2.ext2 is supposed to write to /dev/sdaX >> and not /dev/rd/0. Stracing it and gr

Re: mkfs.ext2 triggerd RAM corruption

2007-05-05 Thread Theodore Tso
On Sat, May 05, 2007 at 03:36:37AM +0200, Bernd Schubert wrote: > distribution: modified debian sarge, in which aspect is the distribution > important for this problem? mkfs2.ext2 is supposed to write to /dev/sdaX > and not /dev/rd/0. Stracing it and grepping for open calls shows that > only /dev/s

Re: mkfs.ext2 triggerd RAM corruption

2007-05-04 Thread Bernd Schubert
Jan-Benedict Glaw wrote: > On Fri, 2007-05-04 16:59:51 +0200, Bernd Schubert <[EMAIL PROTECTED]> > wrote: >> To see whats going on, I copied the entire / (so the initrd) into a >> tmpfs >> root, chrooted into it, also bind mounted the main / into this chroot >> and >> compared several times /bin o

Re: mkfs.ext2 triggerd RAM corruption

2007-05-04 Thread Bernd Schubert
Theodore Tso wrote: > On Fri, May 04, 2007 at 04:59:51PM +0200, Bernd Schubert wrote: >> >> I'm presently rather puzzled, if this is really a kernel bug, its a >> big >> bug. >> >> Summary: The system ramdisk (initrd) gets corrupted while running >> mkfs.ext2 on a local sata disk partition. > >

Re: mkfs.ext2 triggerd RAM corruption

2007-05-04 Thread Theodore Tso
On Fri, May 04, 2007 at 04:59:51PM +0200, Bernd Schubert wrote: > > I'm presently rather puzzled, if this is really a kernel bug, its a big bug. > > Summary: The system ramdisk (initrd) gets corrupted while running > mkfs.ext2 on a local sata disk partition. What distribution are you using? Wh

Re: mkfs.ext2 triggerd RAM corruption

2007-05-04 Thread Jan-Benedict Glaw
On Fri, 2007-05-04 16:59:51 +0200, Bernd Schubert <[EMAIL PROTECTED]> wrote: > To see whats going on, I copied the entire / (so the initrd) into a tmpfs > root, chrooted into it, also bind mounted the main / into this chroot and > compared several times /bin of chroot/bin and the bind-mounted /bi

mkfs.ext2 triggerd RAM corruption

2007-05-04 Thread Bernd Schubert
Hi, I'm presently rather puzzled, if this is really a kernel bug, its a big bug. Summary: The system ramdisk (initrd) gets corrupted while running mkfs.ext2 on a local sata disk partition. Reproduced on kernel versions: vanilla 2.6.16 - 2.6.20 (<2.6.16 doesn't run on any of the systems I can