From: Chris Mason <chris.mason@oracle.com>
To: Steven Pratt <slpratt@austin.ibm.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: nodatacsum broken?
Date: Mon, 16 Nov 2009 12:23:27 -0500 [thread overview]
Message-ID: <20091116172327.GD27677@think> (raw)
In-Reply-To: <4B017C63.5000600@austin.ibm.com>
On Mon, Nov 16, 2009 at 10:22:59AM -0600, Steven Pratt wrote:
> Did we break the ability to run with -o nodatacsum somewhere along
> the way? I had not run just this option in a while (usually doing
> nodatacow which implies nodatacsum). Just did a full run with just
> nodatacsum and it looks like we still did csums.
>
> from proc/mounts:
>
> /dev/ffsbdev1 on /mnt/ffsb1 type btrfs (rw,nodatacsum)
^^^^^^^^^^^^^^
This should be mount -o nodatasum.
2.6.33 will have a patch from Sage to fail mounting when we don't
recognize the option instead of silently pretending it worked. I just
didn't want to introduce it this late in the 2.6.32-rc series.
-chris
next prev parent reply other threads:[~2009-11-16 17:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-16 16:22 nodatacsum broken? Steven Pratt
2009-11-16 16:27 ` Chris Mason
2009-11-16 16:51 ` Steven Pratt
2009-11-16 17:23 ` Chris Mason [this message]
2009-11-16 17:40 ` Steven Pratt
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=20091116172327.GD27677@think \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=slpratt@austin.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox