From: Chris Murphy <lists@colorremedies.com>
To: Jon Ander MB <jonandermonleon@gmail.com>
Cc: Hugo Mills <hugo@carfax.org.uk>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Unable to delete or change ro flag on subvolume/snapshot
Date: Wed, 7 Aug 2019 10:04:53 -0600 [thread overview]
Message-ID: <CAJCQCtTBSRQ-b2HudtzmR-XAaB7BuVR9=6CLdCf5EqBP0TWtFg@mail.gmail.com> (raw)
In-Reply-To: <CACa3q1yonNJY+74XfwoUxq_8ahcTjaSgO76auMt7Oe9NT2TpFg@mail.gmail.com>
On Wed, Aug 7, 2019 at 3:33 AM Jon Ander MB <jonandermonleon@gmail.com> wrote:
>
> Hi! Thanks for the reply!
> First: I am (g)root,, yes :)
> Second: The snapshot was taken in ro mode, the fs is not ro and the
> rest of the snapshots and volumes work as intended (rw)
>
> Thanks
>
> On Wed, Aug 7, 2019 at 11:04 AM Hugo Mills <hugo@carfax.org.uk> wrote:
> >
> > On Wed, Aug 07, 2019 at 10:37:43AM +0200, Jon Ander MB wrote:
> > > Hi!
> > > I have a snapshot with the read only flag set and I'm currently unable
> > > to delete it or change the ro setting
> > > btrfs property set -ts /path/t/snapshot ro false
> > > ERROR: failed to set flags for /path/t/snapshot: Operation not permitted
> > >
> > > Deleting the snapshot is also a no-go:
> > >
> > > btrfs subvolume delete /path/t/snapshot
> > > Delete subvolume (no-commit): '/path/t/snapshot'
> > > ERROR: cannot delete '/path/t/snapshot': Operation not permitted
> >
> > First question: are you running those commands as root?
> >
> > Second question: has the FS itself gone read-only for some reason?
> > (e.g. corruption detected).
> >
> > Hugo.
> >
> > >
> > > The snapshot information:
> > >
> > > btrfs subvolume show /path/t/snapshot
> > > /path/t/snapshot
> > > Name: snapshot
> > > UUID: 66a145da-a20d-a44e-bb7a-3535da400f5d
> > > Parent UUID: f1866638-f77f-e34e-880d-e2e3bec1c88b
> > > Received UUID: 66a145da-a20d-a44e-bb7a-3535da400f5d
> > > Creation time: 2019-07-31 12:00:30 +0200
> > > Subvolume ID: 23786
> > > Generation: 1856068
> > > Gen at creation: 1840490
> > > Parent ID: 517
> > > Top level ID: 517
> > > Flags: readonly
> > > Snapshot(s):
> > >
> > >
> > > Any idea of what can I do?
Maybe strace the failing command, and see if that provides a hint
what's going on?
--
Chris Murphy
prev parent reply other threads:[~2019-08-07 16:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-07 8:37 Unable to delete or change ro flag on subvolume/snapshot Jon Ander MB
2019-08-07 9:04 ` Hugo Mills
2019-08-07 9:33 ` Jon Ander MB
2019-08-07 16:04 ` Chris Murphy [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='CAJCQCtTBSRQ-b2HudtzmR-XAaB7BuVR9=6CLdCf5EqBP0TWtFg@mail.gmail.com' \
--to=lists@colorremedies.com \
--cc=hugo@carfax.org.uk \
--cc=jonandermonleon@gmail.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).