From: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
To: users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org,
mniederle-RbZlAiThDcE@public.gmane.org
Subject: Re: Some problems
Date: Tue, 26 May 2009 06:39:00 +0900 (JST) [thread overview]
Message-ID: <20090526.063900.00723960.ryusuke@osrg.net> (raw)
In-Reply-To: <20090524.175101.94865345.ryusuke-sG5X7nlA6pw@public.gmane.org>
On Sun, 24 May 2009 17:51:01 +0900 (JST), Ryusuke Konishi wrote:
> > >rmcp 685
> > rmcp: 685: operation not permitted
> >
> > What's the cause of this message? (rmcp also failed for all other snapshots;
> > the failed rmcp did not produce any kernel message)
>
> rmcp is allowed only for plain checkpoints.
> So, you have to change it to the plain checkpoint like
>
> # chcp cp 685 1330 ...
> # rmcp 685 ...
>
> Actually, you don't have to do the rmcp because the garbage collection
> will delete plain checkpoints.
>
> I remember someone asked a simliar question before.
>
> I think we should make the error message more user-friendly. And we
> should allow force option of rmcp to remove snapshots; the current
> force option does not have this meaning.
I found the current error code against the removal for snapshots is
badly assigned, and rmcp cannot distinguish it from real permission
errors.
So, first I'm thinking to change the error code to EBUSY or something.
Regards,
Ryusuke Konishi
prev parent reply other threads:[~2009-05-25 21:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1243047601.4877.users@nilfs.org>
[not found] ` <mailman.1.1243047601.4877.users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org>
2009-05-23 20:11 ` Some problems Dipl.-Ing. Michael Niederle
2009-05-24 8:51 ` Ryusuke Konishi
[not found] ` <20090524.175101.94865345.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-05-25 21:39 ` Ryusuke Konishi [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=20090526.063900.00723960.ryusuke@osrg.net \
--to=ryusuke-sg5x7nla6pw@public.gmane.org \
--cc=mniederle-RbZlAiThDcE@public.gmane.org \
--cc=users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.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