From: Ulli Horlacher <framstag@rus.uni-stuttgart.de>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: netapp-alike snapshots?
Date: Tue, 22 Aug 2017 20:01:55 +0200 [thread overview]
Message-ID: <20170822180155.GM14804@rus.uni-stuttgart.de> (raw)
In-Reply-To: <ab52f32.7ade2c3f.15e0af46ee9@gmail.com>
On Tue 2017-08-22 (19:19), A L wrote:
> Perhaps using a bind mount? It would look and work the same as a ordinary fs. Just need to make sure du uses one filesystem.
>
> ---- From: Ulli Horlacher <framstag@rus.uni-stuttgart.de> -- Sent: 2017-08-22 - 18:57 ----
>
> > On Tue 2017-08-22 (21:45), Roman Mamedov wrote:
> >
> >> It is beneficial to not have snapshots in-place. With a local directory of
> >> snapshots, issuing things like "find", "grep -r" or even "du" will take an
> >> inordinate amount of time and will produce a result you do not expect.
> >
> > Netapp snapshots are invisible for tools doing opendir()/readdir()
> > One could simulate this with symlinks for the snapshot directory:
> > store the snapshot elsewhere (not inplace) and create a symlink to it, in
> > every directory.
Not only du works recursivly, but also find and with option also ls, grep,
etc.
And it would require a bind mount for EVERY directory. There can be
hundreds... thousends!
--
Ullrich Horlacher Server und Virtualisierung
Rechenzentrum TIK
Universitaet Stuttgart E-Mail: horlacher@tik.uni-stuttgart.de
Allmandring 30a Tel: ++49-711-68565868
70569 Stuttgart (Germany) WWW: http://www.tik.uni-stuttgart.de/
REF:<ab52f32.7ade2c3f.15e0af46ee9@gmail.com>
next prev parent reply other threads:[~2017-08-22 18:01 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 13:22 netapp-alike snapshots? Ulli Horlacher
2017-08-22 13:44 ` Peter Becker
2017-08-22 14:24 ` Ulli Horlacher
2017-08-22 16:08 ` Peter Becker
2017-08-22 16:48 ` Ulli Horlacher
2017-08-22 16:45 ` Roman Mamedov
2017-08-22 16:57 ` Ulli Horlacher
2017-08-22 17:19 ` A L
2017-08-22 18:01 ` Ulli Horlacher [this message]
2017-08-22 18:36 ` Peter Grandi
2017-08-22 20:48 ` Ulli Horlacher
2017-08-23 7:18 ` number of subvolumes Ulli Horlacher
2017-08-23 8:37 ` A L
2017-08-23 16:48 ` Ferry Toth
2017-08-24 17:45 ` Peter Grandi
2017-08-31 6:49 ` Ulli Horlacher
2017-08-31 11:18 ` Austin S. Hemmelgarn
2017-08-31 14:38 ` Michał Sokołowski
2017-08-31 16:18 ` Duncan
2017-09-01 10:21 ` ein
2017-09-01 11:47 ` Austin S. Hemmelgarn
2017-08-24 19:40 ` Marat Khalili
2017-08-24 21:56 ` Ferry Toth
2017-08-25 5:54 ` Chris Murphy
2017-08-25 11:45 ` Austin S. Hemmelgarn
2017-08-25 12:55 ` Ferry Toth
2017-08-25 19:18 ` Austin S. Hemmelgarn
2017-08-23 12:11 ` Peter Grandi
2017-08-22 21:53 ` user snapshots Ulli Horlacher
2017-08-23 6:28 ` Dmitrii Tcvetkov
2017-08-23 7:16 ` Dmitrii Tcvetkov
2017-08-23 7:20 ` Ulli Horlacher
2017-08-23 11:42 ` Peter Grandi
2017-08-23 21:13 ` Ulli Horlacher
2017-08-25 11:28 ` Austin S. Hemmelgarn
2017-08-22 17:36 ` netapp-alike snapshots? Roman Mamedov
2017-08-22 18:10 ` Ulli Horlacher
2017-09-09 13:26 ` Ulli Horlacher
2017-09-09 13:36 ` Marc MERLIN
2017-09-09 13:44 ` Ulli Horlacher
2017-09-09 19:43 ` Andrei Borzenkov
2017-09-09 19:52 ` Ulli Horlacher
2017-09-10 7:10 ` A L
2017-09-10 14:54 ` Marc MERLIN
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=20170822180155.GM14804@rus.uni-stuttgart.de \
--to=framstag@rus.uni-stuttgart.de \
--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).