Re: [zfs-discuss] RAID-Z2 won't come online after replacing failed disk
Cindy: AWESOME! Didn't know about that property, I'll make sure I set it :). All I did to replace the drives was to power off the machine (the failed drive had hard-locked the SCSI bus, so I had to anyways). Once the machine was powered off, I pulled the bad drive, inserted the new drive, and powered the machine on. That's when the machine came up showing the pool in a corrupted state. I'm assuming if I had removed the old drive, booted it with the drive missing, let it come up DEGRADED, and then inserted the new drive and did a zpool replace, it would have been fine. So I was going by the guess that zpool didn't know that the disk was replaced, and I was just curious why. -- This message posted from opensolaris.org ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] RAID-Z2 won't come online after replacing failed disk
Tim: I couldn't do a zpool scrub, since the pool was marked as UNAVAIL. Believe me, I tried :) Bob: Ya, I realized that after I clicked send. My brain was a little frazzled, so I completely overlooked it. Solaris 10u7 - Sun E450 ZFS pool version 10 ZFS filesystem version 3 -Dustin -- This message posted from opensolaris.org ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] RAID-Z2 won't come online after replacing failed disk
Okay.. I "fixed" it by powering the server off, removing the new drive, letting the pool come up degraded, and then doing zpool replace. I'm assuming what happened was ZFS saw that the disk was online, tried to use it, and then noticed that the checksums didn't match (of course) and marked the pool as corrupted. The question is why didn't ZFS check the labels on the drive and see that the drive wasn't in the pool and kick it out itself? -- This message posted from opensolaris.org ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
[zfs-discuss] RAID-Z2 won't come online after replacing failed disk
I replaced a bad disk in a RAID-Z2 pool, and now the pool won't come online. Status shows nothing helpful at all. I don't understand why this is, which I should be able to lose 2 drives, and I only replaced one! # zpool status -v pool pool: pool state: UNAVAIL scrub: none requested config: NAMESTATE READ WRITE CKSUM poolUNAVAIL 0 0 0 insufficient replicas raidz2UNAVAIL 0 0 0 corrupted data c2t0d0 ONLINE 0 0 0 c2t1d0 ONLINE 0 0 0 c2t2d0 ONLINE 0 0 0 c2t3d0 ONLINE 0 0 0 c3t0d0 ONLINE 0 0 0 c3t1d0 ONLINE 0 0 0 c3t2d0 ONLINE 0 0 0 c3t3d0 ONLINE 0 0 0 c4t0d0 ONLINE 0 0 0 c4t1d0 ONLINE 0 0 0 c4t2d0 ONLINE 0 0 0 c4t3d0 ONLINE 0 0 0 -- This message posted from opensolaris.org ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] Problems with '..' on ZFS pool
Bingo, they were 0750. Thanks so much, that was the one thing I didn't think of. I thought I was going crazy :). Thanks again! -Dustin -- This message posted from opensolaris.org ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] Problems with '..' on ZFS pool
Forgot to add that a truss shows:
14960: lstat64("/a1000/..", 0xFFBFF7E8)Err#13 EACCES
[file_dac_search]
ppriv shows the error in UFS:
$ ppriv -e -D -s -file_dac_search ls -ld /a1000/..
ls[15022]: missing privilege "file_dac_search" (euid = 100, syscall = 216)
needed at ufs_iaccess+0x110
/a1000/..: Permission denied
However seeing as it only happens for mounts on that 1 ZFS pool, it being a UFS
problem seems highly unlikely.
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
[zfs-discuss] Problems with '..' on ZFS pool
Hello. I have a really weird problem with a ZFS pool on one machine, and it's only with 1 pool on that machine (the other pool is fine). Any non-root users cannot access '..' on any directories where the pool is mounted, eg: /a1000 on a1000 read/write/setuid/devices/nonbmand/exec/xattr/noatime/dev=4010002 on Wed Jan 28 20:55:38 2009 /home on a1000/home read/write/setuid/devices/nonbmand/exec/xattr/noatime/dev=4010005 on Wed Jan 28 20:55:39 2009 $ ls -ld / drwxr-xr-x 28 root root1024 Jan 29 10:09 / $ ls -ld /home drwxr-xr-x 11 root sys 11 Jan 9 14:49 /home $ ls -ld /home/.. /home/..: Permission denied $ ls -ld /a1000/.. /a1000/..: Permission denied $ ls -V / total 1065 drwxr-xr-x 2 root sys2 Dec 1 14:39 a1000 owner@:--:--:deny owner@:rwxp---A-W-Co-:--:allow group@:-w-p--:--:deny group@:r-x---:--:allow everyone@:-w-p---A-W-Co-:--:deny everyone@:r-x---a-R-c--s:--:allow drwxr-xr-x 6 root sys6 Aug 20 11:47 appl owner@:--:--:deny owner@:rwxp---A-W-Co-:--:allow group@:-w-p--:--:deny group@:r-x---:--:allow everyone@:-w-p---A-W-Co-:--:deny everyone@:r-x---a-R-c--s:--:allow lrwxrwxrwx 1 root root 9 Jun 18 2008 bin -> ./usr/bin drwxr-xr-x 3 root sys 512 Jan 28 18:49 boot 0:user::rwx 1:group::r-x #effective:r-x 2:mask:r-x 3:other:r-x drwxr-xr-x 19 root sys 7680 Jan 28 20:54 dev 0:user::rwx 1:group::r-x #effective:r-x 2:mask:r-x 3:other:r-x drwxr-xr-x 2 root sys 512 Jan 28 20:53 devices 0:user::rwx 1:group::r-x #effective:r-x 2:mask:r-x 3:other:r-x drwxr-xr-x 80 root sys 4608 Jan 29 09:40 etc 0:user::rwx 1:group::r-x #effective:r-x 2:mask:r-x 3:other:r-x drwxr-xr-x 2 root sys 512 Jun 18 2008 export 0:user::rwx 1:group::r-x #effective:r-x 2:mask:r-x 3:other:r-x drwxr-xr-x 11 root sys 11 Jan 9 14:49 home owner@:--:--:deny owner@:rwxp---A-W-Co-:--:allow group@:-w-p--:--:deny group@:r-x---:--:allow everyone@:-w-p---A-W-Co-:--:deny everyone@:r-x---a-R-c--s:--:allow drwxr-xr-x 15 root sys 512 Jun 18 2008 kernel 0:user::rwx 1:group::r-x #effective:r-x 2:mask:r-x 3:other:r-x drwxr-xr-x 7 root bin 5632 Jan 28 19:50 lib 0:user::rwx 1:group::r-x #effective:r-x 2:mask:r-x 3:other:r-x drwx-- 2 root root8192 Jun 18 2008 lost+found 0:user::rwx 1:group::--- #effective:--- 2:mask:--- 3:other:--- drwxr-xr-x 2 root sys 512 Jun 18 2008 mnt 0:user::rwx 1:group::r-x #effective:r-x 2:mask:r-x 3:other:r-x dr-xr-xr-x 2 root root 512 Jun 18 2008 net 0:user::r-x 1:group::r-x #effective:r-x 2:mask:r-x 3:other:r-x -rw-r--r-- 1 root root 0 Jun 18 2008 noautoshutdown 0:user::rw- 1:group::r-- #effective:r-- 2:mask:r-- 3:other:r-- drwxr-xr-x 7 root sys7 Jan 28 15:50 opt owner@:--:--:deny owner@:rwxp---A-W-Co-:--:allow group@:-w-p--:--:deny group@:r-x---:--:allow everyone@:-w-p---A-W-Co-:--:deny everyone@:r-x---a-R-c--s:--:allow drwxr-xr-x 40 root sys 1536 Jun 18 2008 platform 0:user::rwx 1:group::r-x #effective:r-x 2:mask:r-x 3:other:r-x drwxr-xr-x 2 root sys2 Jul 29 2008 pool owner@:--:--:deny owner@:rwxp---A-W-Co-:--:allow group@:-w-p--:--:deny group@:r-x---:--:allow everyone@:-w-p---A-W-Co-:--:deny everyone@:r-x---a-R-c--s:--:allow dr-xr-xr-x 76 root root 480032 Jan 29 10:23 proc 0:user::r-x 1:group::r-x #effective:r-x 2:mask:rwx 3:other:r-x drwxr-x--- 12 root root1024 Jan 29 10:09 root 0:user::rwx 1:group::r-x #effective:r-x 2:mask:r-x 3:other:--- drwxr-xr-x 2 root sys 1024 Jan 28 19:37 sbin 0:user::rwx 1:group::r-x #effective:r-x 2:mask:r-x 3:other:r-x -rw-rw-rw- 1 root root1576 Oct 15 12:40 sybinit.err 0:user::rw- 1:group::rw- #effective:rw- 2:mask:rw- 3:other:r
