Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

util_scratch_dir_avail_for_me not working on ZFS filesystem #768

Open
edoapra opened this issue Apr 12, 2023 · 4 comments
Open

util_scratch_dir_avail_for_me not working on ZFS filesystem #768

edoapra opened this issue Apr 12, 2023 · 4 comments
Labels

Comments

@edoapra
Copy link
Collaborator

edoapra commented Apr 12, 2023

Describe the bug
util_scratch_dir_avail_for_me() does not work correctly on FreeBSD zfs filesystem by returning bogus values

Describe settings used

FreeBSD fbsd 13.2-STABLE FreeBSD 13.2-STABLE stable/13-n254954-d94a88d249b0 GENERIC arm64
FreeBSD was used from Qemu
NWChem 7.2.0 plus recent master patches for FreeBSD issues

Attach log files

  avail0,avail1,avail0-avail1                  3180                 3180                    0
  avail0,avail1,avail0-avail1                  3180                 3180                    0
  avail0,avail1,avail0-avail1                  3180                 3180                    0
  avail0,avail1,avail0-avail1                  3180                 3180                    0

 Integral file          = ./c2h4_dat.aoints.0
 Record size in doubles =  65536        No. of integs per rec  =  43688
 Max. records in memory =    185        Max. records in file   =   6041
 No. of bits per label  =      8        No. of bits per value  =     64


 #quartets = 1.222D+05 #integrals = 8.656D+06 #direct =  0.0% #cached =100.0%

To Reproduce
run the QA tests c2h4

@edoapra edoapra added the bug label Apr 12, 2023
@edoapra
Copy link
Collaborator Author

edoapra commented Apr 12, 2023

Workaround
Compiling with USE_NOFSCHECK=1 should fix the problem.
USE_NOIO=1 will avoid I/O altogether

@edoapra
Copy link
Collaborator Author

edoapra commented Apr 12, 2023

This bug might cause some of the #752 failures, unless the Qemu I/O management is the root cause.

edoapra added a commit to edoapra/nwchem that referenced this issue Apr 12, 2023
edoapra added a commit to edoapra/nwchem that referenced this issue Apr 12, 2023
@edoapra edoapra mentioned this issue Apr 13, 2023
edoapra added a commit to edoapra/nwchem that referenced this issue Apr 13, 2023
@klopata
Copy link
Collaborator

klopata commented May 9, 2023

I also see this issue when using ZFS on Linux, thus it is probably related to the ZFS file system and is not BSD-specific.

Ubuntu 22.04, Linux 5.19.0-41
ZFS via kernel module (zfsutils-linux) using pool directly built from NVMe drives (no virtualization)
NWChem 7.2.0

Running the c2h4 test:

 avail0,avail1,avail0-avail1               1241336              1241336                    0
 avail0,avail1,avail0-avail1               1241336              1241336                    0
 avail0,avail1,avail0-avail1               1241336              1241336                    0
 avail0,avail1,avail0-avail1               1241336              1241336                    0

Integral file          = /work/scratch/c2h4_dat.aoints.0
Record size in doubles =  65536        No. of integs per rec  =  43688
Max. records in memory =     63        Max. records in file   =  87351
No. of bits per label  =      8        No. of bits per value  =     64

USE_NOFSCHECK=1 works, as Edo recommends.

edoapra added a commit to edoapra/nwchem that referenced this issue May 9, 2023
edoapra added a commit to edoapra/nwchem that referenced this issue May 10, 2023
@edoapra edoapra mentioned this issue May 10, 2023
@edoapra
Copy link
Collaborator Author

edoapra commented May 20, 2023

util_fsync() still does not seem to work on ZFS filesystems

@edoapra edoapra changed the title util_scratch_dir_avail_for_me not working on FreeBSD zfs util_scratch_dir_avail_for_me not working on ZFS filesystem May 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants