On Thu, Jan 03, 2013 at 03:21:33PM -0600, Phillip Wagstrom wrote:
> Eugen,

Thanks Phillip and others, most illuminating (pun intended).
 
>       Be aware that p0 corresponds to the entire disk, regardless of how it 
> is partitioned with fdisk.  The fdisk partitions are 1 - 4.  By using p0 for 
> log and p1 for cache, you could very well be writing to same location on the 
> SSD and corrupting things.

Does this mean that with 

Part      Tag    Flag     Cylinders         Size            Blocks
  0 unassigned    wm       0 -   668        4.00GB    (669/0/0)     8391936
  1 unassigned    wm     669 - 12455       70.50GB    (11787/0/0) 147856128
  2     backup    wu       0 - 12456       74.51GB    (12457/0/0) 156260608
  3 unassigned    wm       0                0         (0/0/0)             0
  4 unassigned    wm       0                0         (0/0/0)             0
  5 unassigned    wm       0                0         (0/0/0)             0
  6 unassigned    wm       0                0         (0/0/0)             0
  7 unassigned    wm       0                0         (0/0/0)             0
  8       boot    wu       0 -     0        6.12MB    (1/0/0)         12544
  9 unassigned    wm       0                0         (0/0/0)             0

/dev/dsk/c4t1d0p0 /dev/dsk/c4t2d0p0 means the whole disk? 
I thought the backup partition would be that, and that's p2?

>       Personally, I'd recommend putting a standard Solaris fdisk partition on 
> the drive and creating the two slices under that.

Can you please give me the rundown for commands for that?
I seem to partition a Solaris disk every decade, or so, so
I have no idea what I'm doing.

I've redone the

# zpool remove tank0 /dev/dsk/c4t1d0p1 /dev/dsk/c4t2d0p1
# zpool remove tank0 mirror-1

so the pool is back to mice and pumpkins:

  pool: tank0
 state: ONLINE
  scan: scrub in progress since Fri Jan  4 16:55:12 2013
    773G scanned out of 3.49T at 187M/s, 4h15m to go
    0 repaired, 21.62% done
config:

        NAME                       STATE     READ WRITE CKSUM
        tank0                      ONLINE       0     0     0
          raidz3-0                 ONLINE       0     0     0
            c3t5000C500098BE9DDd0  ONLINE       0     0     0
            c3t5000C50009C72C48d0  ONLINE       0     0     0
            c3t5000C50009C73968d0  ONLINE       0     0     0
            c3t5000C5000FD2E794d0  ONLINE       0     0     0
            c3t5000C5000FD37075d0  ONLINE       0     0     0
            c3t5000C5000FD39D53d0  ONLINE       0     0     0
            c3t5000C5000FD3BC10d0  ONLINE       0     0     0
            c3t5000C5000FD3E8A7d0  ONLINE       0     0     0

errors: No known data errors

_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Reply via email to