From: Harshavardhana <harsha@gluster.com>
To: Chris Mason <chris.mason@oracle.com>, linux-btrfs@vger.kernel.org
Subject: Re: ENOTEMPTY on "rm -rf" for snapshot and subvolume
Date: Thu, 08 Apr 2010 14:14:14 -0700 [thread overview]
Message-ID: <4BBE4726.2070708@gluster.com> (raw)
In-Reply-To: <20100408135216.GE1400@think>
On 04/08/2010 06:52 AM, Chris Mason wrote:
>> > But either in that case too returning ENOTEMPTY does confuse a
>> > user a lot. Isn't it valid
>> > just by returning EPERM will explain a lot to users saying that
>> > this is a snapshot of a
>> > subvolume or a parent subvolume which is not supposed to be
>> > deleted this way.
>>
> Good point, eperm might be more intuitive.
>
> -chris
>
Thanks a lot for the inputs sent a patch for that.
Regards
--
Harshavardhana
http://www.gluster.com
prev parent reply other threads:[~2010-04-08 21:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 0:44 ENOTEMPTY on "rm -rf" for snapshot and subvolume Harshavardhana
2010-04-08 13:52 ` Chris Mason
2010-04-08 21:14 ` Harshavardhana [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=4BBE4726.2070708@gluster.com \
--to=harsha@gluster.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 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).