> You can do this with "zpool scrub". It visits every allocated block > and > verifies that everything is correct. It's not the same as fsck in that > scrub can detect and repair problems with the pool still online and > all > datasets mounted, whereas fsck cannot handle mounted filesystems. > > If you really want to use it on an exported pool, you can use zdb, > although it might take some time. Here's an example on a small empty > pool: > > # zpool create -f mypool raidz c4t1d0s0 c4t2d0s0 c4t3d0s0 c4t4d0s0 > c4t5d0s0 > # zpool list mypool > NAME SIZE ALLOC FREE CAP DEDUP HEALTH ALTROOT > mypool 484M 280K 484M 0% 1.00x ONLINE - > # zpool export mypool > # zdb -ebcc mypool ...
what I'm saying is that there are several posts in here where the only solution is to boot onto a live cd and then do an import, due to metadata corruption. This should be doable from the installed system Vennlige hilsener / Best regards roy -- Roy Sigurd Karlsbakk (+47) 97542685 r...@karlsbakk.net http://blogg.karlsbakk.net/ -- I all pedagogikk er det essensielt at pensum presenteres intelligibelt. Det er et elementært imperativ for alle pedagoger å unngå eksessiv anvendelse av idiomer med fremmed opprinnelse. I de fleste tilfeller eksisterer adekvate og relevante synonymer på norsk. _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
