There are still a lot of strange things happening when create and / or removing ufs snapshots on filesystems with SU+J. While investigating random panics while creating snapshots I experienced:
- Deadlocks, freezing the whole system or just any file system activity. Sometime the kernel prints messages like "fsync: giving up on dirty"
- Random panics with different panic strings like "panic: snapacct_ufs2: bad block" or the generic "panic: page fault while in kernel mode". The backtraces were different too.
- Sudden reboots.
- Corrupted filesystems, only repairable by two or more consecutive runs of "fsck -y" in single user mode.
Non of the problems arise when using normal softupdates without journaling. This problems can be seen on several machines and even in VirtualBox, so hardware failure can be ruled out. Looks like some race condition somewhere in the ufs or snapshot code. Further debug information - including file system images - can be provided if necessary.
Non. Smells like a race condition or something like that.
How-To-Repeat: % mount
/dev/ada0p2 on / (ufs, local, journaled soft-updates)
# create some load
% cp -r /usr/src /tmp
# Switch to another tty and create a snapshot
% mksnap_ffs / /.snap/foo1
Repeat this until the box crashes.
For bugs matching the following criteria:
Status: In Progress Changed: (is less than) 2014-06-01
Reset to default assignee and clear in-progress tags.
Mail being skipped