Date: Thu, 23 Aug 2018 20:47:19 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 230851] fsck sets last modified file size to zero on crash on UFS filesystem Message-ID: <bug-230851-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D230851 Bug ID: 230851 Summary: fsck sets last modified file size to zero on crash on UFS filesystem Product: Base System Version: 11.2-STABLE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: bugs@FreeBSD.org Reporter: aliovx@gmail.com On system crash, fsck sets the last modified files size to 0, loosing their content.=20 Step to reproduce 1) edit a file, for example /boot/loader.conf 2) cause a panic, for example sysctl debug.kdb.panic=3D1 On next boot the content of loader.conf is gone, and its size is set to zer= o.=20 I'm not sure if this is an expected behavior, but it is really bad to loose= the content of the last modified files on crash/panic. I don't pretend to find = my last modifications save, but at least the original file.=20 My UFS settings are the following, but I've tried different combinations, mainly playing with the -n and -j options, same result.=20 tunefs: POSIX.1e ACLs: (-a) disabled tunefs: NFSv4 ACLs: (-N) disabled tunefs: MAC multilabel: (-l) disabled tunefs: soft updates: (-n) enabled tunefs: soft update journaling: (-j) enabled tunefs: gjournal: (-J) disabled tunefs: trim: (-t) enabled tunefs: maximum blocks per file in a cylinder group: (-e) 4096 tunefs: average file size: (-f) 16384 tunefs: average number of files in a directory: (-s) 64 tunefs: minimum percentage of free space: (-m) 8% tunefs: space to hold for metadata blocks: (-k) 6408 tunefs: optimization preference: (-o) time tunefs: volume label: (-L) --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-230851-227>