Hi all! I''m running a Solaris 10 Update 6 (10/08) system and had to resilver a zpool. It''s now showing <snip> scrub: resilver completed after 9h0m with 21 errors on Wed Nov 4 22:07:49 2009 </snip> but I haven''t found an option to see what files where affected, Is there any way to do that? Thanks in advance Marcel -- This message posted from opensolaris.org
Marcel Gschwandl schrieb:> Hi all! > > I''m running a Solaris 10 Update 6 (10/08) system and had to resilver a zpool. It''s now showing > > <snip> > scrub: resilver completed after 9h0m with 21 errors on Wed Nov 4 22:07:49 2009 > </snip> > > but I haven''t found an option to see what files where affected, Is there any way to do that? > > Thanks in advance > > MarcelTry zpool status -v <poolname>
Gschwandl Marcel HSLU T&A
2009-Nov-09 09:07 UTC
[zfs-discuss] zpool resilver - error history
Am 09/11/2009 09:57 schrieb "Thomas Maier-Komor" unter <thomas at maier-komor.de>:> Marcel Gschwandl schrieb: >> Hi all! >> >> I''m running a Solaris 10 Update 6 (10/08) system and had to resilver a zpool. >> It''s now showing >> >> <snip> >> scrub: resilver completed after 9h0m with 21 errors on Wed Nov 4 22:07:49 >> 2009 >> </snip> >> >> but I haven''t found an option to see what files where affected, Is there any >> way to do that? >> >> Thanks in advance >> >> Marcel > > Try > > zpool status -v <poolname>I already tried that, it only gives me <snip> errors: No known data errors </snip> During the resilver it showed me some files but not after finishing it. Thanks anyway -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2184 bytes Desc: not available URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20091109/5f391bdb/attachment.bin>
On Mon, 9 Nov 2009, Gschwandl Marcel HSLU T&A wrote:>> >> zpool status -v <poolname> > > I already tried that, it only gives me > > <snip> > errors: No known data errors > </snip>Errors do not necessarily cause data loss. For example, there may have been sufficient redundancy that the error was able to be automatically repaired and so there was no data loss. Metadata always has a redundant copy, and if you are using something like raidz2, then your data still has a redundant copy while resilvering a disk. Bob -- Bob Friesenhahn bfriesen at simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/