search for: f_favail

...t tmpfs                      188376       0    188376   0% /run/user/0 using scripts: python -c 'import os; s = os.statvfs ("/"); print s' posix.statvfs_result(f_bsize=4096, f_frsize=4096, f_blocks=5886149, f_bfree=4802342, f_bavail=4802342, f_files=23556096, f_ffree=23435372, f_favail=23435372, f_flag=4096, f_namemax=255) python -c 'import os; s = os.statvfs ("/boot"); print s' posix.statvfs_result(f_bsize=4096, f_frsize=4096, f_blocks=127147, f_bfree=93815, f_bavail=93815, f_files=512000, f_ffree=511626, f_favail=511626, f_flag=4096, f_namemax=255) and the...

...guestfs_int_mllib_statvfs_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 (...

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.

...ds64.f_bfree = UINT32_MAX; + /* + * If we''re about to cause EOVERFLOW with any of the inode + * counts, cap the value(s) at UINT32_MAX. + */ + if (ds64.f_files > UINT32_MAX) + ds64.f_files = UINT32_MAX; + if (ds64.f_ffree > UINT32_MAX) + ds64.f_ffree = UINT32_MAX; + if (ds64.f_favail > UINT32_MAX) + ds64.f_favail = UINT32_MAX; + + /* + * If necessary, try to avoid EOVERFLOW by increasing f_frsize. + */ if (ds64.f_blocks > UINT32_MAX || ds64.f_bfree > UINT32_MAX || - ds64.f_bavail > UINT32_MAX || ds64.f_files > UINT32_MAX || - ds64.f_ffree > UINT3...

...8 at 12:58:40PM +0800, Chen Fan wrote: >[In guest] >> python -c 'import os; s = os.statvfs ("/"); print s' >> posix.statvfs_result(f_bsize=4096, f_frsize=4096, f_blocks=5886149, >> f_bfree=4802342, f_bavail=4802342, f_files=23556096, >> f_ffree=23435372, f_favail=23435372, f_flag=4096, f_namemax=255) >> >> python -c 'import os; s = os.statvfs ("/boot"); print s' >> posix.statvfs_result(f_bsize=4096, f_frsize=4096, f_blocks=127147, >> f_bfree=93815, f_bavail=93815, f_files=512000, f_ffree=511626, >> f_favail=5...

On Thu, Jan 04, 2018 at 12:58:40PM +0800, Chen Fan wrote: [In guest] > python -c 'import os; s = os.statvfs ("/"); print s' > posix.statvfs_result(f_bsize=4096, f_frsize=4096, f_blocks=5886149, > f_bfree=4802342, f_bavail=4802342, f_files=23556096, > f_ffree=23435372, f_favail=23435372, f_flag=4096, f_namemax=255) > > python -c 'import os; s = os.statvfs ("/boot"); print s' > posix.statvfs_result(f_bsize=4096, f_frsize=4096, f_blocks=127147, > f_bfree=93815, f_bavail=93815, f_files=512000, f_ffree=511626, > f_favail=511626, f_flag=4096,...

...ree - not X+1" is, hmm, >to say it politically correct, "difficult to meet with a filesystem that >does compress/tail-compact". The point I was complaining about with "X free - not X+1" was that the suggested changes cap the values returned in f_files, f_ffree, and f_favail at UINT32_MAX. If a 32-bit statvfs() returns UINT32_MAX for any of these values when a simultaneous 64-bit statvfs() or a statvfs64() would set one or more of those values to a larger value (I don''t care if it is +1, *2, or *1000), I think we have a problem. >The "X not X-1"...

...test.c: In function `main': conftest.c:234: error: storage size of `stfs' isn't known configure:18288: $? = 1 configure: failed program was: -- configure:18912: gcc -c -g -O2 conftest.c >&5 conftest.c: In function `main': conftest.c:247: error: structure has no member named `f_favail' configure:18918: $? = 1 configure: failed program was: -- configure:18970: gcc -c -g -O2 conftest.c >&5 conftest.c: In function `main': conftest.c:247: error: structure has no member named `f_favail' configure:18976: $? = 1 configure: failed program was: -- configure:19295: gcc...

To summarise: >[In guest] > python -c 'import os; s = os.statvfs ("/boot"); print s' > posix.statvfs_result(f_bsize=4096, f_frsize=4096, f_blocks=127147, > f_bfree=93815, f_bavail=93815, f_files=512000, f_ffree=511626, > f_favail=511626, f_flag=4096, f_namemax=255) >[From the host via libguestfs] > # sudo guestfish --ro -d rpm-build-for-7.2 -i statvfs /boot > bsize: 4096 > frsize: 4096 > blocks: 127147 > bfree: 100215 > bavail: 100215 > files: 512000 > ffree: 511626 > favail: 511626 > fsid:...

...int(&msg, st->f_frsize); + buffer_put_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) +{ +...

...t.com> wrote: >To summarise: > >>[In guest] >> python -c 'import os; s = os.statvfs ("/boot"); print s' >> posix.statvfs_result(f_bsize=4096, f_frsize=4096, f_blocks=127147, >> f_bfree=93815, f_bavail=93815, f_files=512000, f_ffree=511626, >> f_favail=511626, f_flag=4096, f_namemax=255) > >>[From the host via libguestfs] >> # sudo guestfish --ro -d rpm-build-for-7.2 -i statvfs /boot >> bsize: 4096 >> frsize: 4096 >> blocks: 127147 >> bfree: 100215 >> bavail: 100215 >> files: 512000 >> ffre...

Hi, I am using CIFS 2.01.01 on HPUX11V2. CIFS is running in ADS security-mode. Winbind is used to map the userers from the W2K3-Domain (german) to an tdb-file. The user mapping works fine, but I have problems with the ACLS: setting the ACLS to a file or folder from windows leads in "access denied". I'm the owner of the object and have full access. The really crazy thing is,

This version doesn't crash or cause hung processes or stuck mountpoints, so that's an improvement. Rich.

This patch is just for review. It enables FUSE support in the API via two new calls, 'guestfs_mount_local' and 'guestfs_umount_local'. FUSE turns out to be very easy to deadlock (necessitating that the machine be rebooted). Running the test from the third patch is usually an effective way to demonstrate this. However I have not yet managed to produce a simple reproducer that

This changes the proposed API slightly. Previously 'mount-local' generating a 'mounted' event when the filesystem was ready, and from the 'mounted' event you had to effectively do a fork. Now, 'mount-local' just initializes the mountpoint and you have to call 'mount-local-run' to enter the FUSE main loop. Between these calls you can do a fork or whatever

...checking for sigaddset... yes checking whether we can use re-entrant gethostbyname_r Linux style... no checking for struct statfs.f_bfree... yes checking for struct statfs.f_bavail... yes checking for struct statfs.f_frsize... no checking for struct statfs.f_ffree... yes checking for struct statfs.f_favail... no checking for struct statfs.f_namelen... no checking for struct statvfs.f_blocks... yes checking for struct msghdr.msg_accrights... no checking for struct sockaddr.sa_len... yes checking for struct sockaddr_un.sun_len... yes checking for scsireq_t.cmd... no checking for sg_io_hdr_t.interface_i...

...nt gethostbyname_r Linux style... yes checking whether linux/joystick.h uses the Linux 2.2+ API... yes checking for struct statfs.f_bfree... yes checking for struct statfs.f_bavail... yes checking for struct statfs.f_frsize... yes checking for struct statfs.f_ffree... yes checking for struct statfs.f_favail... no checking for struct statfs.f_namelen... yes checking for struct statvfs.f_blocks... yes checking for struct msghdr.msg_accrights... no checking for struct sockaddr.sa_len... no checking for struct sockaddr_un.sun_len... no checking for scsireq_t.cmd... no checking for sg_io_hdr_t.interface_id...