[zfs-discuss] just can't import
I'm running a slightly old version of OSOL, I'm sorry I can't remember the version. I had a de-dup dataset and tried to destroy it. The command hung and so did anything else zfs related. I waited half and hour or so, the dataset was only 15G, and rebooted. The machine refused to boot, stuck at Reading ZFS Config. Asking around on the OSOL list someone kindly suggested I try a livecd and import, scrub, export the pool from there. Well the livecd is also hanging on import, anything else zfs hangs. iostat shows some reads but they drop off to almost nothing after 2 mins or so. Truss'ing the import process just loops this over and over: 3134/6: lwp_park(0xFDE02F38, 0) (sleeping...) 3134/6: lwp_park(0xFDE02F38, 0) Err#62 ETIME I wouldn't mind waiting for the pool to right itself, but to my inexperienced eyes it doesn't actually seem to be doing anything. Any tips greatly appreciated, thanks Matt Harrison ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] just can't import
On 04/11/11 04:01 PM, Matt Harrison wrote: I'm running a slightly old version of OSOL, I'm sorry I can't remember the version. I had a de-dup dataset and tried to destroy it. The command hung and so did anything else zfs related. I waited half and hour or so, the dataset was only 15G, and rebooted. The machine refused to boot, stuck at Reading ZFS Config. Asking around on the OSOL list someone kindly suggested I try a livecd and import, scrub, export the pool from there. Well the livecd is also hanging on import, anything else zfs hangs. iostat shows some reads but they drop off to almost nothing after 2 mins or so. Truss'ing the import process just loops this over and over: 3134/6:lwp_park(0xFDE02F38, 0)(sleeping...) 3134/6:lwp_park(0xFDE02F38, 0) Err#62 ETIME I wouldn't mind waiting for the pool to right itself, but to my inexperienced eyes it doesn't actually seem to be doing anything. Any tips greatly appreciated, Hello again, Two suggestions spring to main: Try to import read only. Try a recovery import, zpool import -Fn should tell you if the pool can be imported. It may take a while! -- Ian. ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] just can't import
On Sun, Apr 10, 2011 at 9:01 PM, Matt Harrison wrote: > I had a de-dup dataset and tried to destroy it. The command hung and so did > anything else zfs related. I waited half and hour or so, the dataset was > only 15G, and rebooted. How much RAM does the system have? Dedup uses a LOT of memory, and it can take a long time to destroy dedup'd datasets. If you keep waiting, it'll eventually return. It could be a few hours or longer. > The machine refused to boot, stuck at Reading ZFS Config. Asking around on The system resumed the destroy that was in progress. If you let it sit, it'll eventually complete. > Well the livecd is also hanging on import, anything else zfs hangs. iostat > shows some reads but they drop off to almost nothing after 2 mins or so. Likewise, it's trying to complete the destroy. Be patient and it'll complete. Never versions of Open Solaris or Solaris 11 Express may complete it faster. > Any tips greatly appreciated, Just wait... -B -- Brandon High : bh...@freaks.com ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] just can't import
On 11/04/2011 05:25, Brandon High wrote: On Sun, Apr 10, 2011 at 9:01 PM, Matt Harrison wrote: I had a de-dup dataset and tried to destroy it. The command hung and so did anything else zfs related. I waited half and hour or so, the dataset was only 15G, and rebooted. How much RAM does the system have? Dedup uses a LOT of memory, and it can take a long time to destroy dedup'd datasets. If you keep waiting, it'll eventually return. It could be a few hours or longer. The machine refused to boot, stuck at Reading ZFS Config. Asking around on The system resumed the destroy that was in progress. If you let it sit, it'll eventually complete. Well the livecd is also hanging on import, anything else zfs hangs. iostat shows some reads but they drop off to almost nothing after 2 mins or so. Likewise, it's trying to complete the destroy. Be patient and it'll complete. Never versions of Open Solaris or Solaris 11 Express may complete it faster. Any tips greatly appreciated, Just wait... -B Thanks for the replies, The machine only has 4G RAM I believe. It's time I should be heading to bed so I'll let it sit overnight, and if I'm still stuck with it I'll give Ian's recent suggestions a go and report back. Many thanks Matt ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] How to rename rpool. Is that recommended ?
Cindy, Here is what I was trying to do.. I have some scripts 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. To build new ldom, create a new Clone, asssign it to Control Domain as a 'vdisk', edit files in vdisk as required for giving a new hostname, IP, etc, then unassign vdisk from control domain, and assign it back to the guest domain. As control domain is already booted from 'rpool', importing another rpool from vdisk required renaiming the rpool on vdisk. But, I couldn't see how rpool on vdisk can be renamed back to its original name 'rpool' after the files in it have been updated. I think, the solution here is to have different name for boot pool on control domain and on the ldom boot disk (one being Cloned) Thanks Arjun On Fri, Apr 8, 2011 at 10:46 PM, Cindy Swearingen < cindy.swearin...@oracle.com> wrote: > Arjun, > > Yes, you an choose any name for the root pool, but an existing > limitation is that you can't rename the root pool by using the > zpool export/import with new name feature. > > Too much internal boot info is tied to the root pool name. > > What info are you changing? Instead, could you create a new BE > and update the info in the new BE. > > Creating a new BE is the best solution. > > Another solution is to create a mirrored root pool and then use the > zpool split option to create an identical root pool (that is then > imported with a new name, like rpool2), but this identical root pool > won't be bootable either. You would then need to mount rpool2's file > systems and copy whatever data you needed. > > Thanks, > > Cindy > > > > > On 04/08/11 01:24, Arjun YK wrote: > >> Hi, >> >> Let me add another query. >> I would assume it would be perfectly ok to choose any name for root >> pool, instead of 'rpool', during the OS install. Please suggest >> otherwise. >> >> Thanks >> Arjun >> >> On 4/8/11, Arjun YK wrote: >> >>> Hello, >>> >>> I have a situation where a host, which is booted off its 'rpool', need >>> to temporarily import the 'rpool' of another host, edit some files in >>> it, and export the pool back retaining its original name 'rpool'. Can >>> this be done ? >>> >>> Here is what I am trying to do: >>> >>> # zpool import -R /a rpool temp-rpool >>> # zfs set mountpoint=/mnt temp-rpool/ROOT/s10_u8 >>> # zfs mount temp-rpool/ROOT/s10_u8 >>> ### For example, edit /a/mnt/etc/hosts >>> # zfs set mountpoint=/ temp-rpool/ROOT/s10_u8 >>> # zfs export temp-rpool--> But, I want to give temp-rpool its >>> original name 'rpool' before or after this export. >>> >>> I cannot see how this can be achieved. So, I decided to live with the >>> name 'temp-rpool'. But, is renaming 'rpool' recommended or supported >>> parctice ? >>> >>> Any help is appreciated. >>> >>> Thanks >>> Arjun >>> >>> ___ >> zfs-discuss mailing list >> zfs-discuss@opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss >> > ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
