search for: nvlists

Hello, I have a dual boot with Windows 7 64 bit enterprise edition and Opensolaris build 134. This is on Sun Ultra 40 M1 workstation. Three hard drives, 2 in ZFS mirror, 1 is shared with Windows. Last 2 days I was working in Windows. I didn''t touch the hard drives in any way except I once opened Disk Management to figure out why a external USB hard drive is not being listed.

This morning we got a fault management message from one of our production servers stating that a fault in one of our pools had been detected and fixed. Looking into the error using fmdump gives: fmdump -v -u 90ea244e-1ea9-4bd6-d2be-e4e7a021f006 TIME UUID SUNW-MSG-ID Oct 22 09:29:05.3448 90ea244e-1ea9-4bd6-d2be-e4e7a021f006 FMD-8000-4M Repaired

Hi, Yesterday I got all my disks in two zpool disconected. They are not real disks - LUNS from StorageTek 2530 array. What could that be - a failing LSI card or a mpt driver in 2009.06? After reboot got four disks in FAILED state - zpool clear fixed things with resilvering. Here is how it started (/var/adm/messages) Feb 23 12:39:03 nexus scsi: [ID 365881 kern.info] /pci at 0,0/pci10de,5d at

Hello, I''ve been using Nexentastore Community Edition with no issues now for a while now, however last week I was going to rebuild a different system so I started to copy all the data off that to my to a raidz2 volume on me CE system. This was going fine until I noticed that they copy was stalled, as well as the entire system was non-responsive. I let it sit for several hours with no

2. update ZFS in libfsimage from illumos for pygrub diff -r 7c12aaa128e3 -r c2e11847cac0 tools/libfsimage/Rules.mk --- a/tools/libfsimage/Rules.mk Thu Oct 24 22:46:20 2013 +0100 +++ b/tools/libfsimage/Rules.mk Sat Oct 26 20:03:06 2013 +0400 @@ -2,11 +2,19 @@ include $(XEN_ROOT)/tools/Rules.mk CFLAGS += -Wno-unknown-pragmas -I$(XEN_ROOT)/tools/libfsimage/common/

Hi all, First, I''ll say my intent is not to spam a bunch of lists, but after posting to opensolaris-discuss I had someone communicate with me offline that these lists would possibly be a better place to start. So here we are. For those on all three lists, sorry for the repetition. Second, this message is meant to solicit help in diagnosing the issue described below. Any hints on

...k) where the author discussed the initial graph-based VDEV indexation, with each VDEV referring to about 3 neighbors; during import/scan it was possible to either find all devices or deduce that some (and which) are missing. But due to some drawbacks of that ASCII based implementation they moved to NVLists. I wonder if such required-device interpolation is done now, or there can be as many VDEVs as can fit into the 112KB of NVList size? That''s about all I can ask for teh first 10 pages of spec text ;) Thanks, //Jim Klimov

...rk but I''m just guessing. Are there any good documents that cover the structure of SMI and/or EFI disk labels? If not can someone point me to the relevant structs on OpenSolaris? Is there any plan to make the ZFS on-disk specification a little more complete? The structure of XDR packed nvlists for instance isn''t documented at all. Thanks, -Chase

...00000000000 > > nvlist version: 0 > version = 0x0 > class = list.suspect > uuid = 4f6725c1-509f-eba4-8774-e627e1925461 > code = SUNOS-8000-KL > diag-time = 1328314280 870353 > de = fmd:///module/software-diagnosis > fault-list-sz = 0x1 > fault-list = (array of embedded nvlists) > (start fault-list[0]) > nvlist version: 0 > version = 0x0 > class = defect.sunos.kernel.panic > certainty = 0x64 > asru = > sw:///:path=/var/crash/bofh-sol/.4f6725c1-509f-eba4-8774-e627e1925461 > resource = > sw:///:path=/var/crash/bofh-sol/.4f6725c1-509f-eba4-8774-e62...

I have a huge problem with space maps on thumper. Space maps takes over 3GB and write operations generates massive read operations. Before every spa sync phase zfs reads space maps from disk. I decided to turn on compression for pool ( only for pool, not filesystems ) and it helps. Now space maps, intent log, spa history are compressed. Not I''m thinking about disabling checksums. All

Hello all, I have an oi_148a PC with a single root disk, and since recently it fails to boot - hangs after the copyright message whenever I use any of my GRUB menu options. Booting with an oi_148a LiveUSB I had around since installation, I ran some zdb traversals over the rpool and zpool import attempts. The imports fail by running the kernel out of RAM (as recently discussed in the list with

...08-01-16 -- For storing the wrapped per dataset encryption keys as a (hidden) property I have been using PROP_TYPE_STRING. However this isn''t really correct since they aren''t strings but binary data. Should I a) add PROP_TYPE_BINARY - which I would likely map to uint8_array for nvlists. Or b) base64 encode the wrapped key and store it in PROP_TYPE_STRING -- Darren J Moffat

Author: gavinm Repository: /hg/zfs-crypto/gate Revision: 78871a9ce8d1373b87f1fa84c7b657d028f873c1 Log message: 6390211 amd64 panicsys() is always called with on_panic_stack == 1 6406417 ereport_size not big enough for nvlist bloat Files: update: usr/src/uts/common/sys/fm/util.h update: usr/src/uts/i86pc/cpu/amd_opteron/ao_mca.c update: usr/src/uts/intel/ia32/ml/i86_subr.s

Yesterday morning I awoke to alerts from my SAN that one of my OS disks was faulty, FMA said it was in hardware failure. By the time I got to work (1.5 hours after the email) ALL of my pools were in a degraded state, and "tank" my primary pool had kicked in two hot spares because it was so discombobulated. ------------------- EMAIL ------------------- List of faulty resources:

Hi forum, I did something stupid the other day, managed to connect an external disk that was part of zpool A such that it appeared in zpool B. I realised as soon as I had done zpool status that zpool B should not have been online, but it was. I immediately switched off the machine, booted without that disk connected and destroyed zpool B. I managed to get zpool A back and all of my data appears

Hi all, It would appear that I have a zpool corruption issue to deal with... pool is exported, but upon trying to import it, server panics.  Are there any tools available on a zpool that is in an exported state?  I''ve got a separate test bed in which I''m trying to recreate, but I keep getting messages to the effect of need to import the pool first.  Suggestions? thanks Jay

Hi, I hope there''s someone here who can possibly provide some assistance. I''ve had this read problem now for the past 2 months and just can''t get to the bottom of it. I have a home snv_111b server, with a zfs raid pool (4 x Samsung 750GB SATA drives). The motherboard is a ASUS M2N68-CM (4 SATA ports) with an Athlon LE1620 single core CPU and 4GB of RAM. I am using it

Hi all, Sorry for the newbie question, but I''ve looked at the docs and haven''t been able to find an answer for this. I''m working with a system where the pool has already been configured and want to determine what the configuration is. I had thought that''d be with zpool status -v <poolname>, but it doesn''t seem to agree with the

I decided to take a stab at 6601421 dladm set-linkprop should support multiple -p options along with some related linkprop fixes, but when I looked into dladm.c, was surprised to find that "dladm_parse_props()" is called from do_create_aggr and do_create_vlan in addition to the expected (by me, at least) do_create_vnic *linkprop functions. What happened here? Why do we pass in

I encountered a strange libzfs behavior while testing a zone fix and want to make sure that I found a genuine bug. I''m creating zones whose zonepaths reside in ZFS datasets (i.e., the parent directories of the zones'' zonepaths are ZFS datasets). In this scenario, zoneadm(1M) attempts to create ZFS datasets for zonepaths. zoneadm(1M) has done this for a long time (since