linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josef Bacik <jbacik@fusionio.com>
To: Goffredo Baroncelli <kreijack@inwind.it>
Cc: Josef Bacik <JBacik@fusionio.com>,
	Wendy Cheng <s.wendy.cheng@gmail.com>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] Btrfs-progs: detect if the disk we are formatting is a ssd V2
Date: Mon, 23 Jul 2012 13:06:52 -0400	[thread overview]
Message-ID: <20120723170652.GM2118@localhost.localdomain> (raw)
In-Reply-To: <500D835D.6060105@inwind.it>

On Mon, Jul 23, 2012 at 11:01:17AM -0600, Goffredo Baroncelli wrote:
> On 07/23/2012 02:46 PM, Josef Bacik wrote:
> > On Fri, Jul 20, 2012 at 04:38:59PM -0600, Wendy Cheng wrote:
> 
> >> However, this should have been a task for the admin (or whoever types
> >> this mkfs command). It is not a filesystem's job to assume how the
> >> firmware works and silently ignore the DUP request, *unless* there is
> >> a standard specification clearly describes linux devices that claim to
> >> be not "rotational" should behave this way.
> >>
> > 
> > The admin can still use -m dup if he wants the added possiblity of protection,
> > this just makes the default not dup.  
> 
> Josef,
> 
> this was clear to us with the the code at hand. However, what was
> pointed out is that is change of a well established behaviour without
> documenting it not informing it.
> 
> I don't arguing about the rationale, what I am telling is : ok to the
> change but you have to inform the user.
> 
> Saying "but the user can revert the change passing '-m dup'" is not a
> valid response, because the user *could* revert the change if he *would*
> be informed about the change.
> 

Yeah sorry Goffredo I agree and I changed it locally, I just haven't sent it out
yet.  Thanks,

Josef

  reply	other threads:[~2012-07-23 17:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-20 19:15 [PATCH] Btrfs-progs: detect if the disk we are formatting is a ssd V2 Josef Bacik
2012-07-20 19:36 ` Goffredo Baroncelli
2012-07-20 22:38   ` Wendy Cheng
2012-07-23 12:46     ` Josef Bacik
2012-07-23 17:01       ` Goffredo Baroncelli
2012-07-23 17:06         ` Josef Bacik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-07-23 17:22 Josef Bacik
2012-11-01 13:51 Josef Bacik

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=20120723170652.GM2118@localhost.localdomain \
    --to=jbacik@fusionio.com \
    --cc=kreijack@inwind.it \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=s.wendy.cheng@gmail.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;
as well as URLs for NNTP newsgroup(s).