You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The zfs version I have is 0.6.5.4 (rebooted after installing the package):
# dpkg -l | grep zfs
ii libzfs2 0.6.5.4-1~trusty amd64 Native OpenZFS filesystem library for Linux
ii mountall 2.53-zfs1 amd64 filesystem mounting tool
ii ubuntu-zfs 8~trusty amd64 Native ZFS filesystem metapackage for Ubuntu.
ii zfs-dkms 0.6.5.4-1~trusty amd64 Native OpenZFS filesystem kernel modules for Linux
ii zfs-doc 0.6.5.4-1~trusty amd64 Native OpenZFS filesystem documentation and examples.
ii zfsutils 0.6.5.4-1~trusty amd64 Native OpenZFS management utilities for Linux
The "junk" file is copied from a MySQL database file. I tried creating a large file with dd:
# dd if=/dev/zero of=junk2 bs=1024000 count=400000
# time rm junk2
real 0m0.002s
user 0m0.000s
sys 0m0.000s
but as seen, it is removed without issue. Obviously dd a file and cp a file are different.
I originally encountered the problem when dropping a large table (300GB) in MySQL database, and found this is due to the removal of the database file, so rm a large file is more basic issue.
The text was updated successfully, but these errors were encountered:
OK, I filed under openzfs/zfs#4227, thanks. I read the FAQ and thought that I should file here, but I read it again, it is for package issues not for packaged zfs issues.
Here is a demonstration of the problem:
The top processes are things like:
The zfs version I have is 0.6.5.4 (rebooted after installing the package):
The "junk" file is copied from a MySQL database file. I tried creating a large file with dd:
but as seen, it is removed without issue. Obviously dd a file and cp a file are different.
I originally encountered the problem when dropping a large table (300GB) in MySQL database, and found this is due to the removal of the database file, so rm a large file is more basic issue.
The text was updated successfully, but these errors were encountered: