similar to: ZFS Volume Issue

Hello, I am trying to update files on LDOM boot disk from Control Domain, but I can''t get it working fully. I have a setup that allows to quickly deploy LDOM guest domains. The Golden OS Image of guest domain boot disk is on a ZFS Volume. This ZFS Volume has been Snapshot and Cloned for the quick deployment of guest domains. Filesystem in both the control domain and guest domain is

Gents, We want to understand the mechanism of zfs a bit better. Q: what is the design/algorithm of zfs in terms of reclaiming unused blocks? Q: what criteria is there for zfs to start reclaiming blocks Issue at hand is an LDOM or zone running in a virtual (thin-provisioned) disk on a NFS server and a zpool inside that vdisk. This vdisk tends to grow in size even if the user writes and deletes

Hello, Has anyone encountered the following error message, running Solaris 10 u8 in an LDom. bash-3.00# devfsadm devfsadm: write failed for /dev/.devfsadm_dev.lock: Bad exchange descriptor bash-3.00# zpool status -v rpool pool: rpool state: DEGRADED status: One or more devices has experienced an error resulting in data corruption. Applications may be affected. action: Restore the file in

[Cross-posting to ldoms-discuss] We are occasionally seeing massive time-to-completions for I/O requests on ZFS file systems on a Sun T5220 attached to a Sun StorageTek 2540 and a Sun J4200, and using a SSD drive as a ZIL device. Primary access to this system is via NFS, and with NFS COMMITs blocking until the request has been sent to disk, performance has been deplorable. The NFS server is a

Hello, We have been running into a few issues recently with cpu panics while trying to reboot the control/service domains on various T-series platforms. Has anyone seen the message below? Thanks SunOS Release 5.10 Version Generic_142900-03 64-bit Copyright 1983-2009 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. NOTICE: zfs_parse_bootfs: error 6 Cannot mount root

I have recently upgraded from NexentaStor 2 to NexentaStor 3 and somehow one of my volumes got corrupted. Its showing up as a socket. Has anyone seen this before? Is there a way to get my data back? It seems like it''s still there, but not recognized as a folder. I ran zpool scrub, but it came back clean. Attached is the output of #zdb data/rt 2.0K sr-xr-xr-x 17 root root 17 Jul

Dear all, Background: I have a ZFS volume with the incorrect volume blocksize for the filesystem (NTFS) that it is supporting. This volume contains important data that is proving impossible to copy using Windows XP Xen HVM that "owns" the data. The disparity in volume blocksize (current set to 512bytes!!) is causing significant performance problems. Question : Is there a way to

Hi, since hostid is stored in the label, "zpool import" failed if the hostid dind''t match. Under certain circonstances (ldom failover) it means you have to manually force the zpool import while booting. With more than 80 LDOMs on a single host it will be great if we could configure the machine back to the old behavior where it didn''t failed, maybe with a /etc/sytem

We''ve been experimenting with zfs on OpenSolaris 2008.11. We created a pool in OpenSolaris and filled it with data. Then we wanted to move it to a production Solaris 10 machine (generic_137138_09) so I "zpool exported" in OpenSolaris, moved the storage, and "zpool imported" in Solaris 10. We got: Cannot import ''deadpool'': pool is formatted

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

I''ve installed Open Solaris 2009.06 on a machine with 5 identical 1TB wd green drives to create a ZFS nas. The intended install is one drive dedicated to the OS and the remaining 4 drives in a raidz1 configuration. The install is working fine, but creating the raidz1 pool and rebooting is causing the machine report "Cannot find active partition" upon reboot. Below is command

http://defect.opensolaris.org/bz/show_bug.cgi?id=782 Summary: zfs keysource=raw fails with keyscope=dataset when file doesn''t exist Classification: Development Product: zfs-crypto Version: unspecified Platform: Other OS/Version: Solaris Status: NEW Severity: minor Priority: P4

Hi, I may have lost my first zpool, due to ... well, we''re not yet sure. The ''zpool import tank'' causes a panic -- one which I''m not even able to capture via savecore. I''m glad this happened when it did. At home I am in the process of moving all my data from a Linux NFS server to OpenSolaris. It''s something I''d been meaning to do

Suppose I have a storage server that runs ZFS, presumably providing file (NFS) and/or block (iSCSI, FC) services to other machines that are running Solaris. Some of the use will be for LDoms and zones[1], which would create zpools on top of zfs (fs or zvol). I have concerns about variable block sizes and the implications for performance. 1.

For some time now, I have had zfs pool, created (if I remeber this correctly) on my x86 opensolaris, with zfs version 6, and have it accessable on my Leopard Mac. I ran the ZFS beta on the Leopard beta with no problems at all. I''ve now installed the latest zfs RW build on my Leopard and it work nicely readwrite on my macbook. It is a pool consisting of one whoe disk. The Leopard says:

I have zfs on my base T5210 box installed with LDOMS (v.1.0.3). Every time I try to jumpstart my Guest machine, I get the following error. ERROR: One or more disks are found, but one of the following problems exists: - Hardware failure - The disk(s) available on this system cannot be used to install Solaris Software. They do not have a valid label. If you want to use the

Hi, I''m trying to track down an error with a 64bit x86 OpenSolaris 2009.06 ZFS shared via iSCSI and an Ubuntu 10.04 client. The client can successfully log in, but no device node appears. I captured a session with wireshark. When the client attempts a "SCSI: Inquiry LUN: 0x00", OpenSolaris sends a "SCSI Response (Check Condition) LUN:0x00" that contains the

Hello, I''m new to OpenSolaris and ZFS so my apologies if my questions are naive! I''ve got solaris express (b52) and a zfs mirror, but this command locks up my box within 5 seconds: % cmp first_4GB_file second_4GB_file It''s not just these two 4GB files, any serious work in the filesystem (but I suspect the larger the file the worse it gets) bring the box to its knees.

Hello, I have read much about ZFS and I find it great, especially the checksums against silent data corruption and the COW writing policy and the snapshots and of course the storage pooling. But there are some points I have problems with: - What happens to the pools if the machine is shut down and rebooted? Are the pools automatically exported and imported again on boot up? Where is the

Hi, I have a zfs volume that''s exported via iscsi for my wife''s Mac to use for Time Machine. I''ve just built a new machine to house my "big" pool, and installed build 129 on it. I''d like to start using COMSTAR for exporting the iscsi targets, rather than the older iscsi infrastructure. I''ve seen quite a few tutorials on how to use