6 марта 2016 г. 19:34:02 CET, Reginald Beardsley via illumos-discuss <[email protected]> пишет: > FYI > > After numerous attempts to replicate the problem and not succeeding I > went to work on the system disks. > > I booted oi151_a8 from the DVD, imported and scrubbed the pools. No > problems. I then exported the pools and rebooted s10_u8. Came up > fine. Scrub of rpool went fine with larger pools currently being > scrubbed. Nothing to suggest any problems. > > Cosmic ray or bit rot? My 3/60 would crash on a tape operation a few > days after booting using a custom kernel linked without superfluous > drivers. Worked fine right after reboot. It was actually completely > predictable. Boot system & try tape. All workee. Wait 2 days. Try > tape again. Sys panicee. With the stock kernel the bad bit mapped to > a device I didn't have. > > So I gave up trying to save 256kB of DRAM. >
Regarding the zfs part of your report - probably, when you booted another OS (installer, failsafe) to import your rpool as just another data pool, it went the full protocol - looking for pool and vdev guids and mapping them together for a real world view. Zpool exporting saved the new device paths into labels. Rebooting allowed grub to report your current bootpath topology, and this time it was correct. I guess something like this... Jim -- Typos courtesy of K-9 Mail on my Samsung Android ------------------------------------------- illumos-discuss Archives: https://www.listbox.com/member/archive/182180/=now RSS Feed: https://www.listbox.com/member/archive/rss/182180/21175430-2e6923be Modify Your Subscription: https://www.listbox.com/member/?member_id=21175430&id_secret=21175430-6a77cda4 Powered by Listbox: http://www.listbox.com
