From: Jens Axboe <axboe@suse.de>
To: Arend Freije <afreije@inn.nl>
Cc: Neil Brown <neilb@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: RAID-1 and Reiser4 issue: umount hangs
Date: Wed, 31 May 2006 11:36:44 +0200 [thread overview]
Message-ID: <20060531093644.GL29535@suse.de> (raw)
In-Reply-To: <447D5F7C.8020401@inn.nl>
On Wed, May 31 2006, Arend Freije wrote:
> You're probably right. I found several posts on the linux-kernel list
> involving problems with write barrier support in combination with SATA
> and ext3 . So I tried:
>
> # mkfs -t ext3 /dev/md/0
> # mount -o barrier=1 /dev/md/0 /mnt
> # cp -a $src /mnt
> # umount /mnt
>
> And indeed, umount hangs now as well.
> So it seems to be a linux-kernel issue after all...
Can you please try 2.6.17-rc5?
--
Jens Axboe
next prev parent reply other threads:[~2006-05-31 9:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-27 22:14 RAID-1 and Reiser4 issue: umount hangs Arend Freije
2006-05-27 22:46 ` Neil Brown
2006-05-28 9:45 ` Arend Freije
2006-05-28 23:49 ` Neil Brown
2006-05-31 9:18 ` Arend Freije
2006-05-31 9:36 ` Jens Axboe [this message]
2006-06-01 18:52 ` Arend Freije
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060531093644.GL29535@suse.de \
--to=axboe@suse.de \
--cc=afreije@inn.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox