> Hello all, > > I've been running OpenSolaris on my personal > fileserver for about a year and a half, and it's been > rock solid except for having to upgrade from 2009.06 > to a dev version to fix some network driver issues. > About a month ago, the motherboard on this computer > died, and I upgraded to a better motherboard and > processor. This move broke the OS install, and > instead of bothering to try to figure out how to fix > it, I decided on a reinstall. All my important data > (including all my virtual hard drives) are stored on > a separate 3 disk raidz pool. > > In attempting to import the pool, I realized that I > had upgraded the zpool to a newer version than is > supported in the live CD, so I installed the latest > dev release to allow the filesystem to mount. After > mounting the drives (with a zpool import -f), I > noticed that some files might be missing. After > installing virtualbox and booting up a WinXP VM, this > issue was confirmed. > > Files before 2/10/2010 seem to be unharmed, but the > next file I have logged on 2/19/2010 is missing. > Every file created after this date is also missing. > The machine had been rebooted several times before > the crash with no issues. For the week or so prior > to the machine finally dying for good, it would > boot, last a few hours, and then crash. These files > were fine during that period. > > One more thing of note: when the machine suffered > critical hardware failure, the zpool in issue was at > about 95% full. When I upgraded to new hardware > (after updating the machine), I added two mirrored > disks to the pool to alleviate the space issue until > I could back everything up, destroy the pool, and > recreate it with six disks instead of three. > > Is this a known bug with a fix, or am I out of luck > with these files? > > Thanks, > Austin
Austin, If your raidz pool with important data was damaged in some way by the hardware failures, then a recovery mechanism in recent builds is to discard the last few transactions to get the pool back to a good known state. You would have seen messages regarding this recovery. We might be able to see if this recovery happened if you could provide your zpool history output for this pool. Generally, a few seconds of data transactions are lost, not all of the data after a certain date. Another issue is that VirtualBox doesn't honor cache flushes by default so if the system is crashing with data in play, your data might not be safely written to disk. Thanks, Cindy -- This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
