Its been suggested before and I've heard its in the freebsd port...
support for spindown?
On Fri, Mar 6, 2009 at 11:40 AM, Dave wrote:
> C. Bergström wrote:
>>
>> Bob Friesenhahn wrote:
>>>
>>> I don't know if anyone has noticed that the topic is "google summer of
>>> code". There is only so muc
Thu, Mar 5, 2009 at 1:09 PM, Kyle Kakligian wrote:
>> On Wed, Mar 4, 2009 at 7:59 PM, Richard Elling
>> wrote:
>>> additional comment below...
>>>
>>> Kyle Kakligian wrote:
>>>>
>>>> On Mon, Mar 2, 2009 at 8:30 AM, Blake wrote:
>
On Wed, Mar 4, 2009 at 7:59 PM, Richard Elling wrote:
> additional comment below...
>
> Kyle Kakligian wrote:
>>
>> On Mon, Mar 2, 2009 at 8:30 AM, Blake wrote:
>>
>>>
>>> that link suggests that this is a problem with a dirty export:
>>>
>
On Mon, Mar 2, 2009 at 8:30 AM, Blake wrote:
> that link suggests that this is a problem with a dirty export:
Yes, a loss of power should mean there was no clean export.
On Mon, Mar 2, 2009 at 8:30 AM, Blake wrote:
> maybe try importing on system A again, doing a 'zpool export', waiting
> for co
On Mon, Mar 2, 2009 at 8:30 AM, Blake wrote:
> that link suggests that this is a problem with a dirty export:
Yes, a loss of power should mean there was no clean export.
On Mon, Mar 2, 2009 at 8:30 AM, Blake wrote:
> maybe try importing on system A again, doing a 'zpool export', waiting
> for co
What does it mean for a vdev to have an invalid configuration and how
can it be fixed or reset? As you can see, the following pool can no
longer be imported: (Note that the "last accessed by another system"
warning is because I moved these drives to my test workstation.)
~$ zpool import -f pool0
c
