On Fri, 13 Mar 2009 22:46:19 -0400
Miles Nordin car...@ivy.net wrote:
jcm == James C McPherson james.mcpher...@sun.com writes:
jcm We haven't got mega_sas on SPARC at this point either.
The card Blake found:
http://www.provantage.com/lsi-logic-lsi00117~7LSIG03X.htm
Hello Jorgen,
Friday, March 13, 2009, 1:14:12 AM, you wrote:
JL That is a good point, I had not even planned to support quotas for ZFS
JL send, but consider a rescan to be the answer. We don't ZFS send very
JL often as it is far too slow.
Since build 105 it should be *MUCH* for faster.
--
Sorry, did not mean it as a complaints, it just has been for us. But if
it has been made faster, that would be excellent. ZFS send is very powerful.
Lund
Robert Milkowski wrote:
Hello Jorgen,
Friday, March 13, 2009, 1:14:12 AM, you wrote:
JL That is a good point, I had not even planned to
I just thought of an enhancement to zfs that would be very helpful in
disaster recovery situations - having zfs cache device serial/model
numbers - the information we see in cfgadm -v.
I'm feeling the pain of this now as I try to figure out which disks on
my failed filer belonged to my raidz2
On 14-Mar-09, at 12:09 PM, Blake wrote:
I just thought of an enhancement to zfs that would be very helpful in
disaster recovery situations - having zfs cache device serial/model
numbers - the information we see in cfgadm -v.
+1 I haven't needed this but it sounds very sensible. I can
Toby Thain wrote:
On 14-Mar-09, at 12:09 PM, Blake wrote:
I just thought of an enhancement to zfs that would be very helpful in
disaster recovery situations - having zfs cache device serial/model
numbers - the information we see in cfgadm -v.
+1 I haven't needed this but it sounds very
That's excellent information Richard.
I have just exported the faulted pool (the disks aren't attached), but
what you are suggesting is verified by looking at the cache as it is -
I can see this information for my rpool mirror disks.
One other note - I see that using the old prtvtoc | fmthard
jcm == James C McPherson james.mcpher...@sun.com writes:
jcm As for will it work on sparc - yes, I would expect so. BUT
jcm without fcode it won't be bootable. That's what you are really
jcm asking, isn't it?
just if it will work. I want to add a slog.
jcm It turns out you can
On Sat, Mar 14, 2009 at 12:57 PM, Miles Nordin car...@ivy.net wrote:
jcm == James C McPherson james.mcpher...@sun.com writes:
jcm As for will it work on sparc - yes, I would expect so. BUT
jcm without fcode it won't be bootable. That's what you are really
jcm asking, isn't it?
just
Richard Elling schrieb:
[...]
ZFS maintains a cache of what pools were imported so that at boot time,
it will automatically try to re-import the pool. The file is
/etc/zfs/zpool.cache
and you can view its contents by using zdb -C
If the current state of affairs does not match the cache, then
Florian Ermisch wrote:
Richard Elling schrieb:
[...]
ZFS maintains a cache of what pools were imported so that at boot time,
it will automatically try to re-import the pool. The file is
/etc/zfs/zpool.cache
and you can view its contents by using zdb -C
If the current state of affairs does
I'm still learning and haven't setup anything I can't destroy if it
can be better put together some other way. I would like to save any
updates and customizations so far if possible. But that isn't
critical either.
Originally I installed osol-11 101b (now at 108) on a 60gb disk
partitioned
I think you will be helped by looking at this document:
http://www.solarisinternals.com/wiki/index.php/ZFS_Troubleshooting_Guide#ZFS_Root_Pool_Recommendations_and_Requirements
It addresses many of your questions.
I think the easiest way to back up your OS might be to attach a disk
to the rpool
13 matches
Mail list logo
