Sorry, I guess I'm running out of reasonable ideas then.
One that you can try (or already did) is installing Solaris not by JumpStart or
WANBoot but from original media (DVD or Network Install) to see if the problem
pertains. Maybe your flash image lacks some controller drivers, etc? (I am not
Well, the Sun-supported way is separating /var from the common root.
In our systems we do a more fine-tuned hierarchy of separated /usr /opt /var in
each BE and sub-separated /var/adm /var/log /var/cores /var/crash and /var/mail
shared between boot environments. This requires quite many tricks
Ah, yes, regarding the backdoor to root fs: if you select to have some
not-quoata'ed space hogs in the same pool as your root FS, you can look into
setting a reservation (and/or refreservation) for the root FS datasets. For
example, if your OS installation uses 4Gb and you don't think it would
The thing is- as far as I know the OS doesn't ask the disk to find a place
to fit the data. Instead the OS tracks what space on the disk is free and
then tells the disk where to write the data.
Yes and no, I did not formulate my idea clearly enough, sorry for confusion ;)
Yes - The disks
Thank you for your insight. This is a system that was handed down to me when
another sysadmin went to greener pastures. There were no quotas set on the
system. I used zfs destroy to free up some space and did put a quota on it. I
still have 0 freespace available. I think this is due to the
Hi,
Thanks for the response, Here is my problem.
I have a zfs stream back up took on zfs version 15, currently i have upgraded
my OS, so new zfs version is 22. Restore process went well from old stream
backup to new zfs pool. but on reboot i got error unable to mount pool tank.
So there is
On Thu, May 12, 2011 at 12:23:55PM +1000, Daniel Carosone wrote:
They were also sent from an ashift=9 to an ashift=12 pool
This reminded me to post a note describing how I made pools with
different ashift. I do this both for pools on usb flash sticks, and
on disks with an underlying 4k
From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
boun...@opensolaris.org] On Behalf Of Peter Jeremy
Finally, the send/recv protocol is not guaranteed to be compatible
between ZFS versions.
Years ago, there was a comment in the man page that said this. Here it is:
The format
Thanks everyone. Your inputs helped me a lot.
The 'rpool/ROOT' mountpoint is set to 'legacy' as I don't see any reason to
mount it. But I am not certain if that can cause any issue in the future, or
that's a right thing to do. Any suggestions ?
Thanks
Arjun
From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
boun...@opensolaris.org] On Behalf Of Naveen surisetty
I have a zfs stream back up took on zfs version 15, currently i have
upgraded
my OS, so new zfs version is 22. Restore process went well from old stream
backup to new zfs
On Thu, May 12, 2011 at 8:31 PM, Arjun YK arju...@gmail.com wrote:
Thanks everyone. Your inputs helped me a lot.
The 'rpool/ROOT' mountpoint is set to 'legacy' as I don't see any reason to
mount it. But I am not certain if that can cause any issue in the future, or
that's a right thing to do.
I have an outage tonight and would like to swap out the LSI 3801 for an
LSI 9200
Should I zpool export before the swaping the card?
On 04/16/2011 10:45 AM, Roy Sigurd Karlsbakk wrote:
I'm going to wait until the scrub is complete before diving in some
more.
I'm wondering if replacing the
This is a slow operation which can only be done about 180-250 times per second
for very random I/Os (may be more with HDD/Controller caching, queuing and
faster spindles).
I'm afraid that seeking to very dispersed metadata blocks, such as traversing
the
tree during a scrub on a fragmented
On May 12, 2011, at 1:53 PM, Karl Rossing wrote:
I have an outage tonight and would like to swap out the LSI 3801 for an LSI
9200
Should I zpool export before the swaping the card?
A clean shutdown is sufficient. You might need to devfsadm -c disk to build
the
device tree.
-- richard
14 matches
Mail list logo
