Re: [zfs-discuss] What about this status report

2010-03-29 Thread Harry Putnam
Just to apologize This not only sounds lame but IS pretty lame. Somehow in reading the output of `zpool status POOL', I just blew right by the URL included there: http://www.sun.com/msg/ZFS-8000-9P Which has quite a decent discussion of what it means. _

Re: [zfs-discuss] What about this status report

2010-03-29 Thread Tonmaus
Both are driver modules for storage adapters Properties can be reviewed in the documentation: ahci: http://docs.sun.com/app/docs/doc/816-5177/ahci-7d?a=view mpt: http://docs.sun.com/app/docs/doc/816-5177/mpt-7d?a=view ahci has a man entry on b133, as well. cheers, Tonmaus -- This message posted

Re: [zfs-discuss] What about this status report

2010-03-29 Thread Harry Putnam
Harry Putnam writes: > Ethan writes: > >>> Assuming your drives support SMART, I'd install smartmontools and see if >> there are any SMART errors on the drive. While the absence of SMART errors > > [...] > >> I've had trouble getting smartmontools to work with some of my >> controllers/drives in

Re: [zfs-discuss] What about this status report

2010-03-28 Thread Tonmaus
Yes. Basically working here. All fine under ahci, some problems under mpt (smartctl says that WD1002fbys wouldn't allow to store smart events, which I think is probably nonsense.) Regards, Tonmaus -- This message posted from opensolaris.org ___ zfs-d

Re: [zfs-discuss] What about this status report

2010-03-28 Thread Harry Putnam
Ethan writes: >> Assuming your drives support SMART, I'd install smartmontools and see if > there are any SMART errors on the drive. While the absence of SMART errors [...] > I've had trouble getting smartmontools to work with some of my > controllers/drives in opensolaris, and have had better

Re: [zfs-discuss] What about this status report

2010-03-27 Thread Ethan
On Sat, Mar 27, 2010 at 18:50, Bob Friesenhahn wrote: > On Sat, 27 Mar 2010, Harry Putnam wrote: > >> >> So its not a serious matter? Or maybe more of a potentially serious >> matter? >> > > It is difficult to say if this is a serious matter or not. It should not > have happened. The severity

Re: [zfs-discuss] What about this status report

2010-03-27 Thread Bob Friesenhahn
On Sat, 27 Mar 2010, Harry Putnam wrote: So its not a serious matter? Or maybe more of a potentially serious matter? It is difficult to say if this is a serious matter or not. It should not have happened. The severity depends on the cause of the problem (which may be difficult to figure o

Re: [zfs-discuss] What about this status report

2010-03-27 Thread Ian Collins
On 03/28/10 10:02 AM, Harry Putnam wrote: Bob Friesenhahn writes: On Sat, 27 Mar 2010, Harry Putnam wrote: What to do with a status report like the one included below? What does it mean to have an unrecoverable error but no data errors? I think that this summary means tha

Re: [zfs-discuss] What about this status report

2010-03-27 Thread Giovanni Tirloni
On Sat, Mar 27, 2010 at 6:02 PM, Harry Putnam wrote: > Bob Friesenhahn writes: > > > On Sat, 27 Mar 2010, Harry Putnam wrote: > > > >> What to do with a status report like the one included below? > >> > >> What does it mean to have an unrecoverable error but no data errors? > > > > I think that

Re: [zfs-discuss] What about this status report

2010-03-27 Thread Harry Putnam
Bob Friesenhahn writes: > On Sat, 27 Mar 2010, Harry Putnam wrote: > >> What to do with a status report like the one included below? >> >> What does it mean to have an unrecoverable error but no data errors? > > I think that this summary means that the zfs scrub did not encounter > any reported r

Re: [zfs-discuss] What about this status report

2010-03-27 Thread Bob Friesenhahn
On Sat, 27 Mar 2010, Harry Putnam wrote: What to do with a status report like the one included below? What does it mean to have an unrecoverable error but no data errors? I think that this summary means that the zfs scrub did not encounter any reported read/write errors from the disks, but o

[zfs-discuss] What about this status report

2010-03-27 Thread Harry Putnam
What to do with a status report like the one included below? What does it mean to have an unrecoverable error but no data errors? Is it just a matter of `clearing' this device? But what would have prompted such a report then? Also note the numeral 7 in the CKSUM column for device c3d1s0. What