From: Alexander Zarochentsev <zam@namesys.com>
To: reiserfs-list@namesys.com
Cc: Arend Freije <afreije@inn.nl>
Subject: Re: RAID-1 and Reiser4 issue: umount hangs
Date: Wed, 31 May 2006 11:13:47 +0400 [thread overview]
Message-ID: <200605311113.48131.zam@namesys.com> (raw)
In-Reply-To: <447C9AFA.90400@inn.nl>
On Tuesday 30 May 2006 23:20, Arend Freije wrote:
> Alexander Zarochentsev wrote:
> > Hello,
> >
> > On Tuesday 30 May 2006 00:17, Arend Freije wrote:
> >> Hi,
> >>
> >> I'm using Reiser4 for my filesystems on disk (/dev/sda) , and it
> >> works just fine. Recently I bought a second disk (/dev/sdb) for
> >> RAID-1 mirroring. With mdadm I created a degraded raid-1 array on
> >> /dev/md/0, devices missing,/dev/sdb1. After that I created a
> >> Reiser4 filesystem on /dev/md/0 and mounted it at /mnt. Then I
> >> copied the data from /dev/sda1 to /mnt.
> >
> > would it work better with "no_write_barrier" mount option?
>
> It would indeed. What's the purpose of this option?
It disables write barrier support in reiser4 which may be buggy. It is
not necessary that reiser4 code has a bug, but the elevator, md device
or disk driver code.
> Kind Regards,
>
> Arend
>
>
> !DSPAM:447c9c9d95615939618124!
--
Alex.
next prev parent reply other threads:[~2006-05-31 7:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-29 20:17 RAID-1 and Reiser4 issue: umount hangs Arend Freije
2006-05-30 11:53 ` Alexander Zarochentsev
2006-05-30 19:20 ` Arend Freije
2006-05-31 7:13 ` Alexander Zarochentsev [this message]
2006-05-31 9:06 ` Arend Freije
2006-05-31 10:41 ` PFC
2006-05-30 15:31 ` Vladimir V. Saveliev
-- strict thread matches above, loose matches on Subject: below --
2006-05-27 22:14 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
2006-06-01 5:54 ` Arend Freije
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=200605311113.48131.zam@namesys.com \
--to=zam@namesys.com \
--cc=afreije@inn.nl \
--cc=reiserfs-list@namesys.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.