public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell Coker <russell@coker.com.au>
To: linux-btrfs@vger.kernel.org
Subject: confusing snapshot error
Date: Sun, 06 Apr 2014 23:18:10 +1000	[thread overview]
Message-ID: <4511581.MJ1MTiboYl@xev> (raw)

ERROR: cannot snapshot '/home' - Read-only file system

The above error occurs when a read-only snapshot already exists.

I think it would be better if the target name had to be fully qualified and 
gave an error "path already 
exists" or something similar.  While the current behavior mimics the operation 
of mv and is surely 
considered a feature by some people, I don't think that mimicing mv is that 
great a feature and the 
current operation gives misleading errors when a snapshot exists.  I just had 
errors from a bunch of 
systems when daylight savings ended and it would have saved me some time if 
the error was clearer.

If we are going to mimic traditional Unix commands then I think it would be 
good to have functionality 
analogous to "mkdir -p" so that next year my cron jobs just quietly don't try 
to make snapshots twice.


Thanks

-- 
My Main Blog         http://etbe.coker.com.au/
My Documents Blog    http://doc.coker.com.au/




                 reply	other threads:[~2014-04-06 13:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4511581.MJ1MTiboYl@xev \
    --to=russell@coker.com.au \
    --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