Re: [zfs-discuss] Re: Proposal: ZFS hotplug support and autoconfiguration

2007-03-23 Thread Eric Schrock
On Fri, Mar 23, 2007 at 11:31:03AM +0100, Pawel Jakub Dawidek wrote: > > Eric, maybe I'm missing something, but why ZFS depend on devids at all? > As I understand it, devid is something that never change for a block > device, eg. disk serial number, but on the other hand it is optional, so > we ca

Re: [zfs-discuss] Re: Proposal: ZFS hotplug support and autoconfiguration

2007-03-23 Thread Pawel Jakub Dawidek
On Fri, Mar 23, 2007 at 11:31:03AM +0100, Pawel Jakub Dawidek wrote: > On Thu, Mar 22, 2007 at 08:39:55AM -0700, Eric Schrock wrote: > > Again, thanks to devids, the autoreplace code would not kick in here at > > all. You would end up with an identical pool. > > Eric, maybe I'm missing something,

Re: [zfs-discuss] Re: Proposal: ZFS hotplug support and autoconfiguration

2007-03-23 Thread Pawel Jakub Dawidek
On Thu, Mar 22, 2007 at 08:39:55AM -0700, Eric Schrock wrote: > Again, thanks to devids, the autoreplace code would not kick in here at > all. You would end up with an identical pool. Eric, maybe I'm missing something, but why ZFS depend on devids at all? As I understand it, devid is something th

Re: [zfs-discuss] Re: Proposal: ZFS hotplug support and autoconfiguration

2007-03-22 Thread Eric Schrock
On Wed, Mar 21, 2007 at 11:57:42PM -0700, Matt B wrote: > > Literally, someone should be able to make $7/hr with a stack of drives > and the ability to just look or listen to a server to determin which > drive needs to be replaced. > > This means ZFS will need to be able to control the HDD Status

Re: [zfs-discuss] Re: Proposal: ZFS hotplug support and autoconfiguration

2007-03-22 Thread Eric Schrock
On Wed, Mar 21, 2007 at 09:26:35PM -0700, Anton B. Rang wrote: > A couple of questions/comments -- > > Why is the REMOVED state not persistent? It seems that, if ZFS knows > that an administrator pulled a disk deliberately, that's still useful > information after a reboot. Changing the state to FA

[zfs-discuss] Re: Proposal: ZFS hotplug support and autoconfiguration

2007-03-21 Thread Matt B
Autoreplace is currently the biggest advantage that H/W raid controllers have over ZFS and other less advanced forms of S/W raid. I would even go so far as to promote this issue to the forefront as a leading deficiency that is hindering ZFS adoption. Regarding H/W raid controllers things are k

[zfs-discuss] Re: Proposal: ZFS hotplug support and autoconfiguration

2007-03-21 Thread Anton B. Rang
A couple of questions/comments -- Why is the REMOVED state not persistent? It seems that, if ZFS knows that an administrator pulled a disk deliberately, that's still useful information after a reboot. Changing the state to FAULTED is non-intuitive, at least to me. What happens with autoreplace