[Bug 193570] New: File corruption after reboot on Virtio-based FreeBSD guest

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Thu Sep 11 18:48:27 UTC 2014


            Bug ID: 193570
           Summary: File corruption after reboot on Virtio-based FreeBSD
           Product: Base System
           Version: 9.3-RELEASE
          Hardware: amd64
                OS: Any
            Status: Needs Triage
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs at FreeBSD.org
          Reporter: jan at siero.de

Host system: CentOS 6 with included KVM
Guest system: FreeBSD on Virtio drivers

System contains 4K / GPT disks with SSD Caching

System runs stable for about a month. After updating the system with
freebsd-update install, or after upgrading a port using "portmaster" a reboot
was issued.

After reboot, multiple library files in /usr/lib were corrupted.

The corruption manifests itself by messages like: 
/usr/lib/libpam.so.5 Shared object has no run-time symbol table

The MD5 hashes of the files differ with the version on the distribution DVD.

Comparing file contents with their originals using hexdiff, the corruption
manifests itself with the following patterns:
 - Corrupted parts start and end exactly at 4K boundaries
 - A file can have multiple corrupted blocks
 - The corrupted 4K blocks are always exact copies of other (non-corrupted) 4K
blocks of the same file.

The corruption was observed on one system three times over the last 4 months,
on FreeBSD 10.0 RELEASE and on FREEBSD 9.3 RELEASE. After corruption the system
was wiped clean and reinstalled.

/var/log/messages shows no entries explaining any system issues

running fsck on the affected partition: the file system is clean

File systems were created using the following commands (aligning them to 4K)

gpart create -s gpt vtbd0
gpart add -a 1M -s 512k -t freebsd-boot -l exboot vtbd0
gpart add -a 1M -s 5G -t freebsd-ufs -l exrootfs vtbd0
gpart add -a 1M -s 5G -t freebsd-swap -l exswap vtbd0
gpart add -a 1M -s 30G -t freebsd-ufs -l exvarfs vtbd0
gpart add -a 1M -s 4G -t freebsd-ufs -l extmpfs vtbd0
gpart add -a 1M -t freebsd-ufs -l exusrfs vtbd0

gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 vtbd0

newfs -U /dev/gpt/exrootfs
newfs -U /dev/gpt/exvarfs
newfs -U /dev/gpt/extmpfs
newfs -U /dev/gpt/exusrfs

You are receiving this mail because:
You are the assignee for the bug.

More information about the freebsd-bugs mailing list