linux-nilfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: dexen deVries <dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: 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 18:08:26 +0100	[thread overview]
Message-ID: <201102271808.35626.dexen.devries@gmail.com> (raw)
In-Reply-To: <-5130718212985067227@unknownmsgid>

On Sunday 27 of February 2011 16:56:25 you wrote:
> In fact, hard links are not supposed to work but cp --reflink
> *should* work but it does not seem to. cp --reflink is what you would
> need to achieve what you want.

I'm much surprised why hardlink shouldn't work.

I used the `stat' command on a file that's both in snapshot and (uchanged) in 
current filesystem state and both inode and device fields (st_ino and st_dev) 
are the same. Thus I don't get why Linux would consider that a cross-device 
hardlink. After all, it's the same filesystem, just different views of it. 
Perhaps Linux' VFS is to blame...


-- 
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

  reply	other threads:[~2011-02-27 17:08 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 [this message]
2011-02-27 16:02   ` Jérôme Poulin

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=201102271808.35626.dexen.devries@gmail.com \
    --to=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).