Well it appears that the pci-x version of the card might or might not work with
drives bigger than 1TB
Attached WD15EADS to ICH9R on motherboard works fine.
Jeb
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@o
I have a Supermicro AOC-SAT2-MV8 running on snv_130. I have a 6 disk raidz2
pool that has been running great.
Today I added a Western Digital Green 1.5TB WD15EADS so I could create some
scratch space.
But, cfgadm will not assign the drive a dsk/xxx ...
I have tried unconfigure/configure and d
The only problem I see, is data set size. Let me explain (and please correct
if I'm wrong).
ZFS basically compresses 2 things -- metadata and data. And data is at most
128k chunk.
Each chunk is individually compressed, not the whole file.
This should affect dictionary size for the lzo compre
(From the README)
# Jeb Campbell <[EMAIL PROTECTED]>
NOTE: This is last resort if you need your data now. This worked for me, and
I hope it works for you. If you have any reservations, please wait for Sun
to release something official, and don't blame me if your data is gone.
This link worked for me:
http://www.opensolaris.org/jive/thread.jspa?messageID=190763
Thanks for the info, and that did have some good tips!
I think I might try hacking the label on the log device first. I'll post if I
get something working.
If that works, it might be best to make a bit for bi
After having to reset my i-ram card, I can no longer import my raidz pool on
2008.05.
Also trying to import the pool using the zpool.cache causes a kernel panic on
2008.05 and B89 (I'm waiting to try B90 when released).
So I have 2 options:
* Wait for a release that can import after log failure
Ok, here is where I'm at:
My install of OS 2008.05 (snv_86?) will not even come up in single user.
The OS 2008.05 live cd comes up fine, but I can't import my old pool b/c of the
missing log (and I have to import to fix the log ...).
So I think I'll boot from the live cd, import my rootpool, mo
Meant to add that zpool import -f pool doesn't work b/c of the missing log vdev.
All the other disks are there and show up with "zpool import", but it won't
import.
Is there anyway a util could clear the log device vdev from the remaining
raidz2 devices?
Then I could import just a standard rai
Wow -- I had seen Joe Little's blog about i-ram and slog and was using it that
way, and mine just failed also.
I'm not at the point he is with data loss, but I've booted the OS 2008.05
livecd and I can see all the disks (minus the log) in an zpool import.
Please, Please, Please, tell me there i
Just so I'm clear:
You are waiting on the release of Samba 3.0.25 which allows vfs_* modules for
ACLS.
Then you will release vfs_zfsacl.c for Samba 3.0.25+ which would allow ACLS to
work?
Also I would love to beta test if needed -- I've been running Samba 3.0.25 from
subversion just to try an
Ed, thanks for the great work on Samba/ZFS! I will be testing the shadow copy
patch soon.
One thing, on the home dir create, would you want to chown it to the user?
Now if we can just get Samba+ZFS acls, we would really be rocking.
Thanks again,
Jeb
This message posted from opensolaris.or
> IIRC you have to re-create entire raid-z pool to get
> it fixed - just
> rewriting data or upgrading a pool won't do it.
You are correct ...
Now I have to find some place to stick +1TB of temp files ;)
Thanks for the help,
Jeb
This message posted from opensolaris.org
_
> After upgrade you did actually re-create your raid-z
> pool, right?
No, but I did "zpool upgrade -a".
Hmm, I guess I'll try re-writing the data first. I know you have to do that if
you change compression options.
Ok -- rewriting the data doesn't work ...
I'll create a new temp pool and see
I updated to Sol10u3 last night, and I'm still seeing different differences
between "du -h" and "ls -h".
"du" seems to take into account raidz and compression -- if this is correct,
please let me know.
It makes sense that "du" reports actual disk usage, but this makes some scripts
I wrote very
Don't know if you are running current OpenSolaris or can wait for Solaris 10
11/06 (should be released in November).
Either of those will contain raidz2 (which is like raid6 where you lose 2
disks).
For max space with some redundancy, I would make one raidz2 vdev of all 8
disks. You will get
15 matches
Mail list logo