From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Mason Subject: Re: Data-logging and md as / fs bug Date: 07 May 2003 11:23:25 -0400 Message-ID: <1052321005.14616.407.camel@tiny.suse.com> References: <3EB30852.6090402@netscape.net> <200305071641.37361.christian.mayrhuber@gmx.net> <1052318606.14616.394.camel@tiny.suse.com> <200305071652.00627.christian.mayrhuber@gmx.net> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: list-help: list-unsubscribe: list-post: Errors-To: flx@namesys.com In-Reply-To: <200305071652.00627.christian.mayrhuber@gmx.net> List-Id: Content-Type: text/plain; charset="us-ascii" To: Christian Mayrhuber Cc: reiserfs-list On Wed, 2003-05-07 at 10:52, Christian Mayrhuber wrote: > Am Mittwoch, 7. Mai 2003 16:43 schrieb Chris Mason: > > On Wed, 2003-05-07 at 10:41, Christian Mayrhuber wrote: > > > /dev/md0 is reiserfs mounted / and /dev/md1 is swap space, messages are > > > from a Debian woody system. /dev/md0 needs to resync after reboot. > > > /dev/md0 consists of hda1 and hdc1 > > > /dev/md1 consists of hda2 and hdc2 > > > The > > > Here's the output from the failed shutdown: > > > > > > Stopping RAID devices: md: md0 still in use > > > /dev/md0: Device or resource busy > > > > Interesting, I think I understand it. You don't any warnings about > > failures while unmounting /, right? > No warning at all. > I've reiserfsck'ed /dev/hda1 and /dev/hdc1 from a cd boot without md support > to see if there is something corrupt on one drive, but both raid1 disks were > perfectly ok. Ok, it's probably because of the way the journal relocation code grabs the journal device. Since root doesn't really get fully unmounted we've probably got a reference open and that is upsetting the md code. The right fix is probably to skip the bdget when the journal device is not external , and just set journal->j_dev_bd to super->s_bdev. Oleg/namesys, do you see any reason this won't work? -chris