On Jul 9, 2010, at 4:27 AM, George wrote:
>> I think it is quite likely to be possible to get
>> readonly access to your data, but this requires
>> modified ZFS binaries. What is your pool version?
>> What build do you have installed on your system disk
>> or available as LiveCD?
For the record
> I think it is quite likely to be possible to get
> readonly access to your data, but this requires
> modified ZFS binaries. What is your pool version?
> What build do you have installed on your system disk
> or available as LiveCD?
[Prompted by an off-list e-mail from Victor asking if I was stil
On Jun 28, 2010, at 11:27 PM, George wrote:
> Again this core dumps when I try to do "zpool clear storage2"
>
> Does anyone have any suggestions what would be the best course of action now?
Do you have any crahsdumps saved? First one is most interesting one...
__
> I think it is quite likely to be possible to get readonly access to
> your data, but this requires modified ZFS binaries. What is your pool
> version? What build do you have installed on your system disk or
> available as LiveCD?
Sorry, but does this mean if ZFS can't write to the drives, access
On Jul 3, 2010, at 1:20 PM, George wrote:
>> Because of that I'm thinking that I should try
>> to change the hostid when booted from the CD to be
>> the same as the previously installed system to see if
>> that helps - unless that's likely to confuse it at
>> all...?
>
> I've now tried changing
> Because of that I'm thinking that I should try
> to change the hostid when booted from the CD to be
> the same as the previously installed system to see if
> that helps - unless that's likely to confuse it at
> all...?
I've now tried changing the hostid using the code from
http://forums.sun.com
> I think I'll try booting from a b134 Live CD and see
> that will let me fix things.
Sadly it appears not - at least not straight away.
Running "zpool import" now gives
pool: storage2
id: 14701046672203578408
state: FAULTED
status: The pool was last accessed by another system.
action: Th
Aha:
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6794136
I think I'll try booting from a b134 Live CD and see that will let me fix
things.
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.
> Please try
>
> zdb -U /dev/null -ebcsv storage2
r...@crypt:~# zdb -U /dev/null -ebcsv storage2
zdb: can't open storage2: No such device or address
If I try
r...@crypt:~# zdb -C storage2
Then it prints what appears to be a valid configuration but then the same error
message about being unab
On Jun 30, 2010, at 10:48 AM, George wrote:
>> I suggest you to try running 'zdb -bcsv storage2' and
>> show the result.
>
> r...@crypt:/tmp# zdb -bcsv storage2
> zdb: can't open storage2: No such device or address
>
> then I tried
>
> r...@crypt:/tmp# zdb -ebcsv storage2
> zdb: can't open sto
> I suggest you to try running 'zdb -bcsv storage2' and
> show the result.
r...@crypt:/tmp# zdb -bcsv storage2
zdb: can't open storage2: No such device or address
then I tried
r...@crypt:/tmp# zdb -ebcsv storage2
zdb: can't open storage2: File exists
George
--
This message posted from opensola
On Jun 29, 2010, at 1:30 AM, George wrote:
> I've attached the output of those commands. The machine is a v20z if that
> makes any difference.
Stack trace is similar to one bug that I do not recall right now, and it
indicates that there's likely a corruption in ZFS metadata.
I suggest you to
Another related question -
I have a second enclosure with blank disks which I would like to use to take a
copy of the existing zpool as a precaution before attempting any fixes. The
disks in this enclosure are larger than those that the one with a problem.
What would be the best way to do this
I've attached the output of those commands. The machine is a v20z if that makes
any difference.
Thanks,
George
--
This message posted from opensolaris.orgmdb: logging to "debug.txt"
> ::status
debugging crash dump vmcore.0 (64-bit) from crypt
operating system: 5.11 snv_111b (i86pc)
panic messag
On Jun 28, 2010, at 11:27 PM, George wrote:
> I've tried removing the spare and putting back the faulty drive to give:
>
> pool: storage2
> state: FAULTED
> status: An intent log record could not be read.
>Waiting for adminstrator intervention to fix the faulted pool.
> action: Either r
15 matches
Mail list logo
