[Bug 278440] [UFS] unxz makes a file which reports wrong usage block size by /usr/bin/du
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 278440] [UFS] unxz makes a file which reports wrong usage block size by /usr/bin/du"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 278440] [UFS] unxz makes a file which reports wrong usage block size by /usr/bin/du"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 278440] [UFS] unxz makes a file which reports wrong usage block size by /usr/bin/du"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 278440] [UFS] unxz makes a file which reports wrong usage block size by /usr/bin/du"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 278440] [UFS] unxz makes a file which reports wrong usage block size by /usr/bin/du -->(It was just a sparse file, not a BUG)"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Thu, 18 Apr 2024 17:33:46 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278440 Bug ID: 278440 Summary: [UFS] unxz makes a file which reports wrong usage block size by /usr/bin/du Product: Base System Version: 14.0-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: uratan@miomio.jp A file which reports wrong(?) disk block usage size is made when /usr/bin/unxz-ing FreeBSD install image on UFS. See the procedure below. +------------------------------------------------------------------- |% uname -a |FreeBSD oxygen 14.0-RELEASE FreeBSD 14.0-RELEASE #2: Fri Apr 12 13:31:59 JST 2024 uratan@oxygen:/usr/src/sys/i386/compile/OXYGEN i386 |% df . |Filesystem 1M-blocks Used Avail Capacity Mounted on |/dev/ada0p5 3666866 3313160 60356 98% /home |% mount | fgrep home |/dev/ada0p5 on /home (ufs, NFS exported, local, noatime, soft-updates) | |% ls |test0/ |% ls -l test0/ |total 638 |-rwxrw-r-- 1 nobody nobody 668057816 Apr 18 23:28 FreeBSD-14.0-RELEASE-i386-memstick.img.xz* | |% cp -pir test0 test1 | |% cd test1 |% unxz FreeBSD-14.0-RELEASE-i386-memstick.img.xz |% mkdir ../test2 |% rsync FreeBSD-14.0-RELEASE-i386-memstick.img ../test2/ |% cd .. | |% du test* |638 test0 <--- has downloaded *.img.xz >>|909 test1 <--- /usr/bin/unxz it >>|1041 test2 <--- copy *.img by /usr/local/bin/rsync | |% ls -lh test* |test0: |total 638 |-rwxrw-r-- 1 nobody nobody 637M Apr 18 23:28 FreeBSD-14.0-RELEASE-i386-memstick.img.xz* |test1: >>|total 909 >>|-rwxrw-r-- 1 uratan nobody 1.0G Apr 18 23:28 FreeBSD-14.0-RELEASE-i386-memstick.img* |test2: >>|total 1041 >>|-rwxr--r-- 1 uratan nobody 1.0G Apr 19 00:16 FreeBSD-14.0-RELEASE-i386-memstick.img* | |% sha256 test*/Free* |SHA256 (test0/FreeBSD-14.0-RELEASE-i386-memstick.img.xz) = c558a19cf17deed6b93cee28356c1d405e2488127c57b7202cc296486308ac4d |SHA256 (test1/FreeBSD-14.0-RELEASE-i386-memstick.img) = dd8a5d36f424d7d6448fb1350c033025c66909ebeecf8cee03baa6f25d23a640 |SHA256 (test2/FreeBSD-14.0-RELEASE-i386-memstick.img) = dd8a5d36f424d7d6448fb1350c033025c66909ebeecf8cee03baa6f25d23a640 | +------------------------------------------------------------------- Is this a BUG ? of which ? - * - * - note.1 The wrongness is also copied when copying the strange file by /bin/cp, /usr/bin/tar or /bin/cat > xxx. note.2 Also redirecting with 'xzcat *.img.xz > *.img' makes strange file. note.3 /bin/df also reports wrong(?) size. note.4 This phenomenon has been happening on my current home-server using FreeBSD 10.2R(i386). -- You are receiving this mail because: You are the assignee for the bug.