zfs raidz2 - insufficient replicas Post: 302583195

Sponsored Content

Operating Systems Solaris zfs raidz2 - insufficient replicas Post 302583195 by skk on Monday 19th of December 2011 11:14:28 PM

12-20-2011

Registered User

zfs raidz2 - insufficient replicas

I lost my system volume in a power outage, but fortunately I had a dual boot and I could boot into an older opensolaris version and my raidz2 7 drive pool was still fine. I even scrubbed it, no errors. However, the older os has some smb problems so I wanted to upgrade to opensolaris11. I accidentally did the auto install option and it overwrote one of my data drives. This is really important data, but fortunately I have a raidz2, so how bad can it be?... BAD! Booting back into the earlier solaris version I cannot access my pool, This is what zpool status shows:

zpool status
pool: brick3
state: UNAVAIL
scrub: none requested
config:

Code:

    NAME        STATE     READ WRITE CKSUM
    brick3      UNAVAIL      0     0     0  insufficient replicas
      raidz2    UNAVAIL      0     0     0  corrupted data
        c12d0   ONLINE       0     0     0
        c11d1   ONLINE       0     0     0
        c10d1   ONLINE       0     0     0
        c10d0   ONLINE       0     0     0
        c8t0d0  ONLINE       0     0     0
        c8t1d0  ONLINE       0     0     0
        c11d0   ONLINE       0     0     0

I tried to export and re-import it, and I get the following message:

zpool import brick3
cannot import 'brick3': invalid vdev configuration

please please please help, what do I do.

Last edited by Yogesh Sawant; 12-22-2011 at 03:13 AM.. Reason: added code tags

skk

View Public Profile for skk

Find all posts by skk

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

SDS and replicas

Hello, We are using Solstice Disk Suite on Solaris 2.7. We want to add two striped volume with six disks. On each disk, we take a slice and we create the stripe. That I want to know : Is it necessary to add two replicas on the same slice on the new disks, as made before on the others...

2. HP-UX

Insufficient permissions on ftp'ed files from WIN2K to HP-UX

We have an application running on Win2K and this application ftp files to HP-UX using ftpdc as user id. The files are created in HP-UX with following permissions: -rw-r----- 1 ftpdc users 968321 Apr 12 22:57 aaaa.txt There is a job that runs on HP-UX trying to modify this file using the...

3. Solaris

insufficient metadevice database replicas ERROR

First I would like to thank this forum for assisting me in setting up my 1st sunbox. Could not have done it if it had not been for you guys and google :D I have mirrored my box and have SUCCESSFULLY tested booting from the rootdisk and rootmirror successfully. I am now looking at configuring...

4. Solaris

Problem with DiskSuite replicas

Good morning, I have Solstice disk suite installed on my server. One disk broke so I sostitute it. A replica was present on this disk. I had delete and then recreate it with commands metadb -d and metadb -a. Now when I inquire for the status of replicas I see this: stp11# metadb -i ...

5. UNIX for Advanced & Expert Users

insufficient available memory

Hi, when navigating on application webpages (peoplesoft applications) the users receive : INSUFFICIENT AVAILABLE MEMORY. I issued vmstat on UNIX server ( where is hosted Web server and application server and DB). Here is the result : :vmstat 2 10 System configuration: lcpu=4 mem=30720MB...

6. UNIX for Advanced & Expert Users

Issue with insufficient swap or memory space

Hi, When I execute one of my shellscript I am getting the below mentioned error message .This application takes 2input files which have the records counts 26463 and 1178046 exec(2): insufficient swap or memory available. exec(2): insufficient swap or memory available. exec(2): insufficient swap...

7. Solaris

metadevices: how to test metadb (how to corrupt replicas/understanding replicas)

Hi all, I recently started exploring Solaris 10. I am testing metadevices now. I have been reading about the state databases here: 6.State Database (Overview) (Solaris Volume Manager Administration Guide) - Sun Microsystems So I created 3 metadbs on 2 slices (6 in total; c1t1d0s3...

8. Solaris

Solaris Volume Manger - Database Replicas Question - Benefits of Increasing Default Size?

Hey all! I was hoping someone knew anything about this one... I know with Solaris Volume Manager the default Database Replica size is 8192 blocks (4MB approximately) Now I know you can increase this amount but is there any point? The reason I am asking this is that I've setup mirroring on...

9. Solaris

13 disk raidz2 pool lost

Hi guys, I appreciate any help in this regard, we have lost sensitive data in the company. One box with 2 disk mirrored and a 3ware controller handling 13 disks in a raidz2 pool. Suddenly the box restart and keeps "Reading ZFS config" for hours. Unplugging disk by disk we isolate the disk...

LEARN ABOUT OPENDARWIN

systemd-networkd-wait-online.service

SYSTEMD-NETWORKD-WAIT-ONLINE.SERVICE(8) 		     systemd-networkd.service			   SYSTEMD-NETWORKD-WAIT-ONLINE.SERVICE(8)

NAME

       systemd-networkd-wait-online.service, systemd-networkd-wait-online - Wait for network to come online

SYNOPSIS

       systemd-networkd-wait-online.service

       /lib/systemd/systemd-networkd-wait-online

DESCRIPTION

       systemd-networkd-wait-online is a one-shot system service that waits for the network to be configured. By default, it will wait for all
       links it is aware of and which are managed by systemd-networkd.service(8) to be fully configured or failed, and for at least one link to
       gain a carrier.

OPTIONS

       The following options are understood:

       -i, --interface=
	   Network interface to wait for before deciding if the system is online. This is useful when a system has several interfaces which will
	   be configured, but a particular one is necessary to access some network resources. This option may be used more than once to wait for
	   multiple network interfaces. When used, all other interfaces are ignored.

       --ignore=
	   Network interfaces to be ignored when deciding if the system is online. By default, only the loopback interface is ignored. This option
	   may be used more than once to ignore multiple network interfaces.

       --timeout=
	   Fail the service if the network is not online by the time the timeout elapses. A timeout of 0 disables the timeout. Defaults to 120
	   seconds.

SEE ALSO

       systemd(1), systemd-networkd.service(8)

systemd 237												   SYSTEMD-NETWORKD-WAIT-ONLINE.SERVICE(8)