> However while copying my /home partition prior to repartitioning a drive,
> I got an oops in the journaling code... I had just created a new ~2GB ext2
> partition on hda5 (4k blocks, volume label set, otherwise default options)
> using mke2fs 1.18, created a blank 8192000 byte journal.dat file on it,
> mounted it as ext3 with journaling, and was copying everything from the
> old /home via tar. I went and got a soda, then came back to find a
> zombified tar process and an oops in my syslog. :( I tried to copy again,
> got a second oops at the same EIP.
Let me guess, did your copy command avoided overwriting the journal.dat ?
If not it's not surprizing, that's the only way (with soft raid + ext3)
I found to get an oops from ext3.
I reiterate, the ext3 code must protect the journal from user-level
process operation, or we are gonna have serious headaches in the user support
dept. :-(
Daniel
--
[EMAIL PROTECTED] | W3C, INRIA Rhone-Alpes | Today's Bookmarks :
Tel : +33 476 615 257 | 655, avenue de l'Europe | Linux XML libxml WWW
Fax : +33 476 615 207 | 38330 Montbonnot FRANCE | Gnome rpm2html rpmfind
http://www.w3.org/People/all#veillard%40w3.org | RPM badminton Kaffe
