From: Efraim Flashner <efraim@flashner.co.il>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 47379@debbugs.gnu.org
Subject: bug#47379: "statfs" test in tests/syscall.scm fails with BTRFS file systems.
Date: Thu, 25 Mar 2021 12:04:10 +0200 [thread overview]
Message-ID: <YFxgGjhK36kJ8nn6@3900XT> (raw)
In-Reply-To: <c6bbf5ce384c68f46cd473da3af716e95788b3d4.camel@telenet.be>
[-- Attachment #1: Type: text/plain, Size: 2199 bytes --]
On Thu, Mar 25, 2021 at 09:49:08AM +0100, Maxime Devos wrote:
> Hi Guix,
>
> Version:
> guix (GNU Guix) 1155a88308df7649fe74bd5bb8279a4d103ce386
>
> The following test fails:
>
> (start snip)
> test-name: statfs
> location: $HOME/guix/git/guix/tests/syscalls.scm:123
> source:
> + (test-assert
> + "statfs"
> + (let ((fs (statfs "/")))
> + (and (file-system? fs)
> + (> (file-system-block-size fs) 0)
> + (>= (file-system-blocks-available fs) 0)
> + (>= (file-system-blocks-free fs)
> + (file-system-blocks-available fs)))))
> actual-value: #f
> result: FAIL
> (end snip)
>
> Evaluating (statfs "/") from a REPL gives:
>
> scheme@(guix-user)> ((@ (guix build syscalls) statfs) "/")
> $2 = #<<file-system> type: 2435016766 block-size: 4096 blocks: 244189696 blocks-free: 178549974 blocks-available: 178571318 files: 0 free-
> files: 0 identifier: (1111009624 2088757363) name-length: 255 fragment-size: 4096 mount-flags: 1056 spare: (0 0 0 0)>
>
> It seems the following does not hold on my system:
> + (>= (file-system-blocks-free fs)
> + (file-system-blocks-available fs))
>
I'm also running on btrfs
(ins)scheme@(guile-user)> (statfs "/")
$1 = #<<file-system> type: 2435016766 block-size: 4096 blocks: 244049664 blocks-free: 165299045 blocks-available: 165178857 files: 0 free-files: 0 identifier:
(2930232877 3283401406) name-length: 255 fragment-size: 4096 mount-flags: 4128 spare: (0 0 0 0)>
(cmd)scheme@(guile-user)> (>= (file-system-blocks-free (statfs "/")) (file-system-blocks-available (statfs "/")))
$5 = #t
(ins)efraim@3900XT ~$ btrfs filesystem df /
Data, single: total=289.00GiB, used=287.83GiB
System, single: total=32.00MiB, used=48.00KiB
Metadata, single: total=13.00GiB, used=12.07GiB
GlobalReserve, single: total=512.00MiB, used=0.00B
When was the last time you ran btrfs balance? Regardless, we still want
this test to pass on btrfs.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-03-25 10:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 8:49 bug#47379: "statfs" test in tests/syscall.scm fails with BTRFS file systems Maxime Devos
2021-03-25 10:04 ` Efraim Flashner [this message]
2021-03-25 10:16 ` Maxime Devos
2021-03-25 10:25 ` Efraim Flashner
2021-03-26 12:22 ` raid5atemyhomework via Bug reports for GNU Guix
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YFxgGjhK36kJ8nn6@3900XT \
--to=efraim@flashner.co.il \
--cc=47379@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).