https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230851
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: b...@freebsd.org
Reporter: ali...@gmail.com
On system crash, fsck sets the last modified files size to 0, loosing their
content.
Step to reproduce
1) edit a file, for example /boot/loader.conf
2) cause a panic, for example sysctl debug.kdb.panic=1
On next boot the content of loader.conf is gone, and its size is set to zero.
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.
My UFS settings are the following, but I've tried different combinations,
mainly playing with the -n and -j options, same result.
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)
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
