linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: Bryan Henderson <hbryan@us.ibm.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
	akpm@osdl.org, linux-fsdevel@vger.kernel.org,
	viro@ftp.linux.org.uk
Subject: Re: [PATCH 0/8] FUSE improvements + VFS changes
Date: Tue, 25 Oct 2005 21:02:47 +0100	[thread overview]
Message-ID: <20051025200247.GA32540@mail.shareable.org> (raw)
In-Reply-To: <OF660E9A23.A13ED41E-ON882570A5.0056BF5E-882570A5.0058F2A4@us.ibm.com>

Bryan Henderson wrote:
> Besides the scope of statfs, I know another thing that defines the 
> separation between two filesystems:  you can't link or relink across 
> filesystems.  In sshfs, you probably get a failure if you try to move a 
> file from a directory in one remote filesystem to one in another remote 
> filesystem, even though according to the Linux view, they're both in the 
> same filesystem.  (And even if it doesn't fail, it certainly doesn't do 
> what you expect from rename()).

Other things that various software depends on:

   st_dev changes across a mount point (inode number space), so that
   (st_dev, st_ino) uniquely identifies each file (as long as they are
   open, on some filesystems that don't have real inode numbers).  In
   particular, identical (st_dev, st_ino) for two paths imply the
   paths are hard links.

   After finding st_nlink different paths referring to the same
   (st_dev, st_ino) pair, one may assume that's all the links to a
   file.  (That's broken by bind mounts, unfortunately).

-- Jamie

  parent reply	other threads:[~2005-10-25 20:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-24 16:45 [PATCH 0/8] FUSE improvements + VFS changes Miklos Szeredi
2005-10-25  4:27 ` Al Viro
2005-10-25  5:56   ` Miklos Szeredi
2005-10-25  7:04     ` Miklos Szeredi
2005-10-25  8:39       ` Al Viro
2005-10-25  8:55         ` Miklos Szeredi
2005-10-25 16:11           ` Bryan Henderson
2005-10-25 18:20             ` Miklos Szeredi
2005-10-25 20:02             ` Jamie Lokier [this message]
2005-10-25  8:05     ` Al Viro

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=20051025200247.GA32540@mail.shareable.org \
    --to=jamie@shareable.org \
    --cc=akpm@osdl.org \
    --cc=hbryan@us.ibm.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=viro@ftp.linux.org.uk \
    /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).