All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Pratt <slpratt@austin.ibm.com>
To: Chris Mason <chris.mason@oracle.com>,
	linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: nodatacsum broken?
Date: Mon, 16 Nov 2009 11:40:01 -0600	[thread overview]
Message-ID: <4B018E71.3000003@austin.ibm.com> (raw)
In-Reply-To: <20091116172327.GD27677@think>

Chris Mason wrote:
> 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.
>
>   
Oops. My bad. Re-running.

> 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.
>   
Good.

Steve


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


      reply	other threads:[~2009-11-16 17:40 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
2009-11-16 17:40   ` Steven Pratt [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=4B018E71.3000003@austin.ibm.com \
    --to=slpratt@austin.ibm.com \
    --cc=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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.