search for: f_fsid

Currently f_fsid of struct kstatfs returned from ocfs2_statfs() is undefined (vfs layer fills 0 as default). Since in some conditions, f_fsid value might be used as (f_fsid, ino) pair to uniquely identify a file, ocfs2 should return a unique defined f_fsid value from ocfs2_statfs(). Because uuid_str is identified...

Currently f_fsid of struct kstatfs returned from ocfs2_statfs() is undefined (at least it should be filled with 0). Since in some conditions, f_fsid value might be used as (f_fsid, ino) pare to uniquely identify a file, ocfs2 should return a defined unique f_fsid value from ocfs2_statfs(). This patch uses uuid_has...

Currently f_fsid of struct kstatfs returned from ocfs2_statfs() is undefined (vfs layer fills 0 as default). Since in some conditions, f_fsid value might be used as (f_fsid, ino) pair to uniquely identify a file, ocfs2 should return a unique defined f_fsid value from ocfs2_statfs(). This patch uses uuid_hash as a...

Currently f_fsid of struct kstatfs returned from ocfs2_statfs() is undefined (vfs layer fills 0 as default). Since in some conditions, f_fsid value might be used as (f_fsid, ino) pair to uniquely identify a file, ocfs2 should return a unique defined f_fsid value from ocfs2_statfs(). This patch uses uuid_hash as a...

...new filehandles. Signed-off-by: NeilBrown <neilb-l3A5Bk7waGM@public.gmane.org> -- This is a substantially revised version of a patch I posted a while ago. I tried to find a way to do it would hard coding knowledge of btrfs in nfs-utils, but it isn''t possible. For some filesystems, f_fsid is best, for some it is worst. No way to tell the difference. This patch add infrastructure so that if we find a better way to get a good uuid (e.g. a new syscall), we can slot it in for new filehandles, but old filehandles using the old uuid will still work. I believe this is ready for inclusio...

...the configuration script. (1) My version of /usr/include/netinet/in.h did not define in_port_t, causing compiler to fail on channels.c line 2472. Worked around by changing in_port_t to uint16_t on that line. (2) sftp-server.c line 507 buffer_put_int64(&msg, FSID_TO_ULONG(st->f_fsid)); got "incompatible type" error. FSID_HAS_VAL was not defined: checking if f_fsid has val members... no causing FSID_TO_ULONG to be defined in defines.h: # define FSID_TO_ULONG(f) ((f)) but I don't see how this could work---was it intentional that...

...tvfs_free_space (value pathv) +guestfs_int_mllib_statvfs_statvfs (value pathv) { CAMLparam1 (pathv); - CAMLlocal1 (rv); + int64_t f_bsize; + int64_t f_frsize; + int64_t f_blocks; + int64_t f_bfree; + int64_t f_bavail; + int64_t f_files; + int64_t f_ffree; + int64_t f_favail; + int64_t f_fsid; + int64_t f_flag; + int64_t f_namemax; + CAMLlocal2 (rv, v); + +#ifdef HAVE_STATVFS struct statvfs buf; - int64_t free_space; - if (statvfs (String_val (pathv), &buf) == -1) { - perror ("statvfs"); - caml_failwith ("statvfs"); - } + if (statvfs (String_val...

It started out as "this'll be just a simple fix ..." and turned into something a bit over-engineered in the end. Here it is anyway. Rich.

v1 -> v2: - Removed the f_type field from StatVFS.statvfs structure. - New function StatVFS.filesystem_is_remote, written in C. [Thinking about it, this should probably be called ?is_network_filesystem?, but I can change that before pushing]. - Use statvfs instead of fstatvfs, and statfs instead of fstatfs. - Rejigged the comments in builder/builder.ml to make them simpler

v2 -> v3: - Drop gnulib fallback.

Hi, Here''s an implementation of NFS support for btrfs. It does not work in one particular case as described in http://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg00298.html. This uses the btrfs_iget helper introduced previously. Comments ? --- Signed-off-by: Balaji Rao <balajirrao@gmail.com> diff -r 3f0eee804974 Makefile --- a/Makefile Thu Jun 26 10:34:20 2008 -0400

...SIGINFO, 0x7fde2bc1c5d0}, NULL, 8) = 0 rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0 getrlimit(RLIMIT_STACK, {rlim_cur=8192*1024, rlim_max=RLIM64_INFINITY}) = 0 statfs("/sys/fs/selinux", {f_type=SELINUX_MAGIC, f_bsize=4096, f_blocks=0, f_bfree=0, f_bavail=0, f_files=0, f_ffree=0, f_fsid={0, 0}, f_namelen=255, f_frsize=4096, f_flags=ST_VALID|ST_RELATIME}) = 0 statfs("/sys/fs/selinux", {f_type=SELINUX_MAGIC, f_bsize=4096, f_blocks=0, f_bfree=0, f_bavail=0, f_files=0, f_ffree=0, f_fsid={0, 0}, f_namelen=255, f_frsize=4096, f_flags=ST_VALID|ST_RELATIME}) = 0 stat("/sys/...

We are having problems remounting an ext3 filesystem using an external journal device. The filesystem in question was working fine until the server was rebooted. This is what we see on dmesg when trying to mount: EXT3: failed to claim external journal device. The external journal lives on a LVM2 logical volume and it seems to be accessible ( we can dumpe2fs and see filesystem information).

...gt; > rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0 > > getrlimit(RLIMIT_STACK, {rlim_cur=8192*1024, rlim_max=RLIM64_INFINITY}) = 0 > > statfs("/sys/fs/selinux", {f_type=SELINUX_MAGIC, f_bsize=4096, > > f_blocks=0, f_bfree=0, f_bavail=0, f_files=0, f_ffree=0, f_fsid={0, > > 0}, f_namelen=255, f_frsize=4096, f_flags=ST_VALID|ST_RELATIME}) = 0 > > statfs("/sys/fs/selinux", {f_type=SELINUX_MAGIC, f_bsize=4096, > > f_blocks=0, f_bfree=0, f_bavail=0, f_files=0, f_ffree=0, f_fsid={0, > > 0}, f_namelen=255, f_frsize=4096, f_flags=ST_...

...int64(&msg, st->f_blocks); + buffer_put_int64(&msg, st->f_bfree); + buffer_put_int64(&msg, st->f_bavail); + buffer_put_int64(&msg, st->f_files); + buffer_put_int64(&msg, st->f_ffree); + buffer_put_int64(&msg, st->f_favail); + buffer_put_int(&msg, st->f_fsid); + buffer_put_int(&msg, flag); + buffer_put_int(&msg, st->f_namemax); + send_msg(&msg); + buffer_free(&msg); +} + /* parse incoming */ static void @@ -1049,6 +1079,24 @@ } static void +process_extended_statvfs(u_int32_t id) +{ + char *path; + struct statvfs st; + int ret...

...be ignored, since the directory would not be backed up anyway. Then I realized that rsync uses stat to tell that a directory is a mount-point. Is there any other way to get this information? I found statfs(2) and statvfs(2) on my Linux system, but I couldn't get anything useful out of them (f_fsid was always 0). If there is some other approach, it would be nice to use it. That way, when rsync got an IO error, it could check whether the path is a mount-point and ignore the error when one-file-system is set. Andrew

...IZE == 64 */ struct statfs { - uint64_t f_type; - uint64_t f_bsize; + uint32_t f_type; + uint32_t f_bsize; uint64_t f_blocks; uint64_t f_bfree; uint64_t f_bavail; uint64_t f_files; uint64_t f_ffree; __kernel_fsid_t f_fsid; - uint64_t f_namelen; - uint64_t f_frsize; - uint64_t f_spare[5]; + uint32_t f_namelen; + uint32_t f_frsize; + uint32_t f_spare[5]; }; #endif /* _BITSIZE */

please pull from git://charm.itp.tuwien.ac.at/mattems/klibc/.git branch maks. arch/mips/klibc/archconfig.h | 3 +++ klibc/sysconfig.h | 10 ++++++++++ sys/vfs.h | 17 +++++++++++++++++ 3 files changed, 30 insertions(+)

...5d0}, NULL, 8) = 0 > rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0 > getrlimit(RLIMIT_STACK, {rlim_cur=8192*1024, rlim_max=RLIM64_INFINITY}) = 0 > statfs("/sys/fs/selinux", {f_type=SELINUX_MAGIC, f_bsize=4096, > f_blocks=0, f_bfree=0, f_bavail=0, f_files=0, f_ffree=0, f_fsid={0, > 0}, f_namelen=255, f_frsize=4096, f_flags=ST_VALID|ST_RELATIME}) = 0 > statfs("/sys/fs/selinux", {f_type=SELINUX_MAGIC, f_bsize=4096, > f_blocks=0, f_bfree=0, f_bavail=0, f_files=0, f_ffree=0, f_fsid={0, > 0}, f_namelen=255, f_frsize=4096, f_flags=ST_VALID|ST_RELATIME})...

...rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0 >>> getrlimit(RLIMIT_STACK, {rlim_cur=8192*1024, rlim_max=RLIM64_INFINITY}) = 0 >>> statfs("/sys/fs/selinux", {f_type=SELINUX_MAGIC, f_bsize=4096, >>> f_blocks=0, f_bfree=0, f_bavail=0, f_files=0, f_ffree=0, f_fsid={0, >>> 0}, f_namelen=255, f_frsize=4096, f_flags=ST_VALID|ST_RELATIME}) = 0 >>> statfs("/sys/fs/selinux", {f_type=SELINUX_MAGIC, f_bsize=4096, >>> f_blocks=0, f_bfree=0, f_bavail=0, f_files=0, f_ffree=0, f_fsid={0, >>> 0}, f_namelen=255, f_frsize=4096,...