public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrey Kuzmin <andrey.v.kuzmin@gmail.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: snapshot-removal - timeline ?
Date: Wed, 5 Aug 2009 22:28:31 +0400	[thread overview]
Message-ID: <2a31deca0908051128r48cdfd62t2d0fe40c4a9b1a05@mail.gmail.com> (raw)
In-Reply-To: <5D3C1A84-7A56-48CC-9C78-EDC582ED6B54@karlsbakk.net>

On Wed, Aug 5, 2009 at 3:18 PM, Roy Sigurd Karlsbakk <roy@karlsbakk.net=
> wrote:
>
> On 4. aug.. 2009, at 20.33, Chris Mason wrote:
>
>>> It's strange that such a small thing should be delayed so much. If
>>> snapshot removal was working, I'm quite sure we might get more user=
s
>>> and thereby more stable code faster.
>>
>> It's a small feature but it gets deep into the difficult parts of th=
e
>> dentry cache to do it right. =A0So, it definitely isn't easy.
>
>
> I'd say it's a pretty elemetary feature to be able to remove somethin=
g you have created.

Snapshots are somewhat counter-intuitive in many respects: for
instance, one snapshot-capable file-system performs writes to  a
dataset with snapshots _faster_ than to the same dataset w/o
snapshots. Snapshot removal is no exception - it's a bit more complex
than one would think.

Regards,
Andrey

> I know, you can remove the files and so on, but still, having a bunch=
 of old and empty
> snapshots lying around is no good.


>
> roy
> --
> Roy Sigurd Karlsbakk
> (+47) 97542685
> roy@karlsbakk.net
> http://blogg.karlsbakk.net/
> --
> I all pedagogikk er det essensielt at pensum presenteres intelligibel=
t. Det er et element=E6rt imperativ for alle pedagoger =E5 unng=E5 ekse=
ssiv anvendelse av idiomer med fremmed opprinnelse. I de fleste tilfell=
er eksisterer adekvate og relevante synonymer p=E5 norsk.
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs=
" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at =A0http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2009-08-05 18:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-01 12:03 snapshot-removal - timeline ? Roland
2009-08-03 13:04 ` Chris Mason
2009-08-03 14:33   ` Roy Sigurd Karlsbakk
2009-08-03 16:18     ` Chris Mason
2009-08-04  7:52       ` Roy Sigurd Karlsbakk
2009-08-04 15:02         ` Brian Neu
2009-08-04 18:33         ` Chris Mason
2009-08-05 11:18           ` Roy Sigurd Karlsbakk
2009-08-05 11:54             ` Josef Bacik
2009-08-05 18:28             ` Andrey Kuzmin [this message]
2009-08-05 18:46               ` Christian Mikovits
2009-08-05 19:40                 ` Andrey Kuzmin

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=2a31deca0908051128r48cdfd62t2d0fe40c4a9b1a05@mail.gmail.com \
    --to=andrey.v.kuzmin@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