From: Eric Sandeen <sandeen@redhat.com>
To: Gary Hawco <ghawco@cox.net>
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
Theodore Tso <tytso@mit.edu>
Subject: Re: Unable to disable barriers
Date: Wed, 30 Jul 2008 11:37:40 -0500 [thread overview]
Message-ID: <489098D4.7080004@redhat.com> (raw)
In-Reply-To: <3.0.6.32.20080728114837.02425390@pop.west.cox.net>
Gary Hawco wrote:
> Subject pretty much says it all.
>
> For testing purposes I tried to disable barriers in fstab (barriers=0). On
> reboot the filesystem will not mount read/write until barriers are reenabled.
What errors do you get?
> This occurs whether I use ordered data mode or data writeback mode, in both
> Gentoo and Slackware 12.1
>
> Is this behavior by design (that barriers can not be disabled)?
>
> Thanks,
> Gary
Hm, it's not supposed to be :)
Perhaps you just spelled it wrong:
root@inode ~]# mount -o barriers=0 /dev/sdb2 /mnt/test
mount: wrong fs type, bad option, bad superblock on /dev/sdb2,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
[root@inode ~]# mount -o barrier=0 /dev/sdb2 /mnt/test
[root@inode ~]#
-Eric
prev parent reply other threads:[~2008-07-30 16:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-28 11:48 Unable to disable barriers Gary Hawco
2008-07-30 16:37 ` Eric Sandeen [this message]
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=489098D4.7080004@redhat.com \
--to=sandeen@redhat.com \
--cc=ghawco@cox.net \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).