Kyle Kakligian gmail.com> writes:
> I'm not sure why `zfs import` choked on this [typical?] error case,
> but its easy to fix with a very careful dd. I took a different and
> very roundabout approach to recover my data, however, since I'm not
> confident in my 'careful' skills. (after all, where
Alright, I created the links
# ln -s /dev/ad6 /mydev/ad6
...
# ln -s /dev/ad10 /mydev/ad10
and ran 'zpool import -d /mydev'
Nothing - the links in /mydev are all broken.
Thanks again,
Tim
--
This message posted from opensolaris.org
___
zfs-discuss m
On Thu, 15 Jul 2010, Tim Castle wrote:
j...@opensolaris:~# zpool import -d /dev
...shows nothing after 20 minutes
OK, then one other thing to try is to create a new directory, e.g. /mydev,
and create in it symbolic links to only those drives that are part of your
pool.
Based on your label
Thank you for the reply Mark.
I flashed my sata card and it's now compatible with open solaris: I can see all
the remaining good drives.
j...@opensolaris:~# zpool import
pool: files
id: 3459234681059189202
state: UNAVAIL
status: One or more devices contains corrupted data.
action: The po
What does 'zpool import -d /dev' show?
On Wed, 14 Jul 2010, Tim Castle wrote:
My raidz1 (ZFSv6) had a power failure, and a disk failure. Now:
j...@opensolaris:~# zpool import
pool: files
id: 3459234681059189202
state: UNAVAIL
status: One or mor
My raidz1 (ZFSv6) had a power failure, and a disk failure. Now:
j...@opensolaris:~# zpool import
pool: files
id: 3459234681059189202
state: UNAVAIL
status: One or more devices contains corrupted data.
action: The pool cannot be imported due to da
> Check contents of /dev/dsk and /dev/rdsk to see if
> there are some
> missing links there for devices in question. You may
> want to run
>
> devfsadm -c disk -sv
> devfsadm -c disk -Csv
>
> and see if it reports anything.
There were quite a few links it removed, all on c0.
> Try to move c6d
Victor took the words right out of my fingers :-) more below...
Victor Latushkin wrote:
Brian Leonard wrote:
Since you did not export the pool, it may be looking for the wrong
devices. Try this:
zpool export vault
zpool import vault
That was the first thing I tried, with no luck.
Above
Brian Leonard wrote:
Since you did not export the pool, it may be looking for the wrong
devices. Try this:
zpool export vault
zpool import vault
That was the first thing I tried, with no luck.
Above, I used slice 0 as an example, your system may use a
different slice. But you can run zd
> h... export the pool again. Then try simply "zpool import"
> and it should show the way it sees vault. Reply with that output.
zpool export vault
cannot open 'vault': no such pool
zpool import
pool: vault
id: 196786381623412270
state: UNAVAIL
action: The pool cannot be imported d
Brian Leonard wrote:
Since you did not export the pool, it may be looking for the wrong
devices. Try this:
zpool export vault
zpool import vault
That was the first thing I tried, with no luck.
Above, I used slice 0 as an example, your system may use a
different slice. But you ca
> Since you did not export the pool, it may be looking for the wrong
> devices. Try this:
> zpool export vault
> zpool import vault
That was the first thing I tried, with no luck.
> Above, I used slice 0 as an example, your system may use a
> different slice. But you can run zdb -l on all o
Since you did not export the pool, it may be looking for the wrong
devices. Try this:
zpool export vault
zpool import vault
which will clear the old entries out of the zpool.cache and look for
the new devices.
More below...
Brian Leonard wrote:
I had a machine die the other day and take
I had a machine die the other day and take one of its zfs pools with it. I
booted the new machine, with the same disks but a different SATA controller,
and the rpool was mounted but another pool "vault" was not. If I try to import
it I get "invalid vdev configuration". fmdump shows zfs.vdev.ba
SOLVED
According to `zdb -l /dev/rdsk/`, one of my drives was missing
two of its four redundant labels. (#2 and #3) These two are next to
each other at the end of the device so it makes some sense that they
could both be garbled.
I'm not sure why `zfs import` choked on this [typical?] error case,
On 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:
>>>
that link suggests that this is a problem with a dirty ex
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:
>>>
>>
>> Yes, a loss of power should mean there was no clean
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:
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 import
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
that link suggests that this is a problem with a dirty export:
http://www.sun.com/msg/ZFS-8000-EY
maybe try importing on system A again, doing a 'zpool export', waiting
for completion, then moving to system B to import?
On Sun, Mar 1, 2009 at 2:29 PM, Kyle Kakligian wrote:
> What does it mean f
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
22 matches
Mail list logo
