linux-ext4 - Re: Unable to disable barriers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <489098D4.7080004@redhat.com>
Date:	Wed, 30 Jul 2008 11:37:40 -0500
From:	Eric Sandeen <sandeen@...hat.com>
To:	Gary Hawco <ghawco@....net>
CC:	"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>,
	Theodore Tso <tytso@....edu>
Subject: Re: Unable to disable barriers

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@...de ~]# 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@...de ~]# mount -o barrier=0 /dev/sdb2 /mnt/test
[root@...de ~]#

-Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html