Dear all We use iSCSI quite a lot e.g. as backend for our OpenSolaris based fileservers. After updating the machine to b114 we ran into a strange problem. The pool get''s imported (listed by ''zpool list'') but none of it''s ZFS filesystems get mounted. Exporting and reimporting manually fixes the problem as does "zfs mount -a". So far it simply worked, as said till we updated. Any hints? Thomas ----------------------------------------------------------------- GPG fingerprint: B1 EE D2 39 2C 82 26 DA A5 4D E0 50 35 75 9E ED
>>>>> "tn" == Thomas Nau <Thomas.Nau at uni-ulm.de> writes:tn> After updating the machine to b114 we ran into a strange tn> problem. The pool get''s imported (listed by ''zpool list'') but tn> none of it''s ZFS filesystems get mounted. Exporting and tn> reimporting manually fixes the problem as does "zfs mount tn> -a". So far it simply worked, as said till we updated. ``me, too'''' with b71, so the symptom isn''t new. I think this happens for me when the pool is UNAVAILABLE at boot, and then enough devices come on line that it becomes ready. In that case I need to do both zfs mount -a and zfs share -a. (or export/import) For me the main aspect of this problem is zfs mount mounting things in the wrong order: some of the datasets are mounted but not all. If you have nested filesystems, a/A a/A/1 a/A/2 a/B sometimes you can end up with a/A/1, a/A/2, a/B mounted but a/A is not mounted. In this case, the ''a'' filesystem contains empty directories serving as mountpoints a/A/1 and a/A/2, when it should contain only mountpoint a/A (with the deeper two mountpoints inside the a/A filesystem). You have to clear out the incorrect deeper mountpoints before zfs mount -a will work properly again. so on second thought since you say none of your filesystems are mounted, you may have a different symptom. -- READ CAREFULLY. By reading this fortune, you agree, on behalf of your employer, to release me from all obligations and waivers arising from any and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and acceptable use policies ("BOGUS AGREEMENTS") that I have entered into with your employer, its partners, licensors, agents and assigns, in perpetuity, without prejudice to my ongoing rights and privileges. You further represent that you have the authority to release me from any BOGUS AGREEMENTS on behalf of your employer. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 304 bytes Desc: not available URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20090528/b8d8c583/attachment.bin>
Miles, Miles Nordin wrote:>>>>>> "tn" == Thomas Nau <Thomas.Nau at uni-ulm.de> writes: > > tn> After updating the machine to b114 we ran into a strange > tn> problem. The pool get''s imported (listed by ''zpool list'') but > tn> none of it''s ZFS filesystems get mounted. Exporting and > tn> reimporting manually fixes the problem as does "zfs mount > tn> -a". So far it simply worked, as said till we updated. > > ``me, too'''' with b71, so the symptom isn''t new. > > I think this happens for me when the pool is UNAVAILABLE at boot, and > then enough devices come on line that it becomes ready. In that case > I need to do both zfs mount -a and zfs share -a. (or export/import) > > For me the main aspect of this problem is zfs mount mounting things in > the wrong order: some of the datasets are mounted but not all. If you > have nested filesystems, > > a/A > a/A/1 > a/A/2 > a/B > > sometimes you can end up with a/A/1, a/A/2, a/B mounted but a/A is not > mounted. In this case, the ''a'' filesystem contains empty directories > serving as mountpoints a/A/1 and a/A/2, when it should contain only > mountpoint a/A (with the deeper two mountpoints inside the a/A > filesystem). You have to clear out the incorrect deeper mountpoints > before zfs mount -a will work properly again. > > so on second thought since you say none of your filesystems are > mounted, you may have a different symptom.That''s strange. It always worked for us like a charm up till yesterday evening when the upgrade completed. We never ran into any issues you had. Thomas ----------------------------------------------------------------- GPG fingerprint: B1 EE D2 39 2C 82 26 DA A5 4D E0 50 35 75 9E ED