From: "Jérôme Poulin" <jeromepoulin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: dexen deVries <dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: It is not possible to restore file from a mounted snapshot using a hardlink
Date: Sun, 27 Feb 2011 11:02:17 -0500 [thread overview]
Message-ID: <-5862432177062534167@unknownmsgid> (raw)
In-Reply-To: <201102271420.57110.dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Just after replying I noticed you talked about cp= and noticed I sent
to the nilfs mailing list and not btrfs ! So cp --reflink does not
work on NILFS but would be a nice feature :)
Envoyé de mon appareil mobile.
Jérôme Poulin
Solutions G.A.
On 2011-02-27, at 08:20, dexen deVries <dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> Hello,
>
>
> The following is more of a feature request than problem report, actually.
>
> I've mounted an older snapshot and tried to restore (add it to the current
> filesystem state) by creating a hardlink.
> Roughly like:
> mount /dev/sdb3 ~/current
> mount.nilfs2 /dev/sdb3 ~/old -o ro,cp=1234
> cd ~/current
> ln ~/old/file.bin ./restored-file.bin
>
> The `ln' returned `Invalid cross-device link'.
>
> I expected such hardlink to have semantics of re-using all the data blocks &
> metadata of file.bin from snapshot as restored-file.bin, so no duplication of
> data blocks happens.
>
>
> Regards,
> --
> dexen deVries
>
> ``One can't proceed from the informal to the formal by formal means.''
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2011-02-27 16:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-27 13:20 It is not possible to restore file from a mounted snapshot using a hardlink dexen deVries
[not found] ` <201102271420.57110.dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-02-27 15:56 ` Jérôme Poulin
2011-02-27 17:08 ` dexen deVries
2011-02-27 16:02 ` Jérôme Poulin [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=-5862432177062534167@unknownmsgid \
--to=jeromepoulin-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@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;
as well as URLs for NNTP newsgroup(s).