List,
This is probably a silly question, but I've honestly never tried this and don't
have a test machine handy at the moment - can a pool be safely exported and
re-imported later if it is currently resilvering?
In the way of a bit of background, I have a pool made up with thirty or so 4TB
Hi all,
Anybody able to start powertop using some of the available options?
root@nas:/root# powertop -d 1
Segmentation Fault (core dumped)
root@nas:/root# powertop -t 10
Segmentation Fault (core dumped)
root@nas:/root# powertop -d 1 -v
Segmentation Fault (core dumped)
root@nas:/root# powertop
This is probably a silly question, but I¹ve honestly never tried this and
don¹t have a test machine handy at the moment can a pool be safely
exported and re-imported later if it is currently resilvering?
In the way of a bit of background, I have a pool made up with thirty or
so 4TB Seagate
You might also crank up the priority on your resilver, particularly if it
is getting tripped all of the time:
http://broken.net/uncategorized/zfs-performance-tuning-for-scrubs-and-resilvers/
-nld
On Tue, Jun 9, 2015 at 1:31 PM, Dave Pooser dave...@pooserville.com wrote:
This is probably a
On Jun 9, 2015, at 8:05 AM, Robert A. Brock robert.br...@2hoffshore.com
wrote:
List,
This is probably a silly question, but I’ve honestly never tried this and
don’t have a test machine handy at the moment – can a pool be safely exported
and re-imported later if it is currently
On Jun 9, 2015, at 12:00 PM, Narayan Desai narayan.de...@gmail.com wrote:
You might also crank up the priority on your resilver, particularly if it is
getting tripped all of the time:
http://broken.net/uncategorized/zfs-performance-tuning-for-scrubs-and-resilvers/
They are failed as far as OmniOS is concerned, from what I can tell:
Jun 08 01:08:54 710768e8-2f2b-4b3d-9d4b-a85ef5617219 DISK-8000-12 Major
Host: 2hus291
Platform: S5500BC Chassis_id :
Product_sn :
Fault class : fault.io.disk.over-temperature
Affects :
This must have been done millions of times already, but as a newbie I'm
having great difficulty getting a kvm guest inside a zone to network
properly. It seems to me that I've tried every combination of configs I
can think of (except one, no doubt ;) ) but can't get anything outside
the zone
In message 55775165.50...@thestephensdomain.com, Graham Stephens writes:
This must have been done millions of times already, but as a newbie I'm
having great difficulty getting a kvm guest inside a zone to network
URL:http://lists.omniti.com/pipermail/omnios-discuss/2015-March/004477.html
With
I went through this problem a while back. There are some gotchas in
getting them back online and firmware upgraded. The is will not talk to
the drive until it has its firmware upgraded or cleared from the fault
database.
This drives will not flash with multipath enabled either.
I ended up
Fwflash has an issue:
root@2hus291:/root# fwflash -f MegalodonES3-SAS-STD-0004.LOD -d
/devices/pci@0,0/pci8086,340e@7/pci1000,3040@0/iport@f/disk@w5000c50057fbaf01,0:a,raw
fwflash:
sd-GENERIC firmware image verifier: supplied filename
MegalodonES3-SAS-STD-0004.LOD exceeds maximum allowable size
Quoting Dominik Hassler hassl...@gmx.li:
you need a dedicated vnic for the kvm. I assume you have one vnic
and use that one for the zone so it is not exclusive for the kvm
guest anymore and won't work to my knowledge. You can always bind
VNC to a unix socket so you don't acutally need a
I gave this a go on 151012 (014 isn't available as an AMI yet, and I
can't get the 006 AMI to accept a ssh key pair on instance creation),
and saw the same thing. powertop appears to segfault in
string_to_decimal / libc.so.1.
I then tried rebuilding powertop from the OmniTI illumos-gate build
13 matches
Mail list logo
