With Nevada Build 98 I realize a slow zpool import of my pool which holds my user and archive data on my laptop. The first time it was realized during the boot if Solaris tells me to mount zfs filesystems (1/9) and then works for 1-2 minutes until it goes ahead. I hear the disk working but have no clue what happens here. So I checked to zpool export and import, and with this import it is also slow (takes around 90 seconds to import and with b97 it took 5 seconds). Has anyone an idea what the reason could be ? I also had created 2 ZVOL''s under one filesysystem. Now I removed the upper filesystem (and expected that zfs will also remove the both zvols). But now on zpool exports it complains about these two unknown datasets as: "dataset does not exist" Any comments and ideas how to "really" remove the zvols and what''s the issue with slow zpool import ? Detlef
Detlef, I presume you have about 9 filesystems. How many snapshots do you have ? Thanks and regards, Sanjeev. On Mon, Sep 22, 2008 at 03:59:34PM +0200, Detlef Drewanz at Sun.COM wrote:> With Nevada Build 98 I realize a slow zpool import of my pool which > holds my user and archive data on my laptop. > > The first time it was realized during the boot if Solaris tells me to > mount zfs filesystems (1/9) and then works for 1-2 minutes until it goes > ahead. I hear the disk working but have no clue what happens here. > So I checked to zpool export and import, and with this import it is also > slow (takes around 90 seconds to import and with b97 it took 5 seconds). > Has anyone an idea what the reason could be ? > > I also had created 2 ZVOL''s under one filesysystem. Now I removed the > upper filesystem (and expected that zfs will also remove the both > zvols). But now on zpool exports it complains about these two unknown > datasets as: "dataset does not exist" > > Any comments and ideas how to "really" remove the zvols and what''s the > issue with slow zpool import ? > > Detlef > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
I have no snapshots in this zpool. On 09/22/08 16:09, Sanjeev wrote:> Detlef, > > I presume you have about 9 filesystems. How many snapshots do you have ? > > Thanks and regards, > Sanjeev. > > On Mon, Sep 22, 2008 at 03:59:34PM +0200, Detlef Drewanz at Sun.COM wrote: >> With Nevada Build 98 I realize a slow zpool import of my pool which >> holds my user and archive data on my laptop. >> >> The first time it was realized during the boot if Solaris tells me to >> mount zfs filesystems (1/9) and then works for 1-2 minutes until it goes >> ahead. I hear the disk working but have no clue what happens here. >> So I checked to zpool export and import, and with this import it is also >> slow (takes around 90 seconds to import and with b97 it took 5 seconds). >> Has anyone an idea what the reason could be ? >> >> I also had created 2 ZVOL''s under one filesysystem. Now I removed the >> upper filesystem (and expected that zfs will also remove the both >> zvols). But now on zpool exports it complains about these two unknown >> datasets as: "dataset does not exist" >> >> Any comments and ideas how to "really" remove the zvols and what''s the >> issue with slow zpool import ?
On 09/22/08 06:59, Detlef Drewanz at Sun.COM wrote:> With Nevada Build 98 I realize a slow zpool import of my pool which > holds my user and archive data on my laptop. > > The first time it was realized during the boot if Solaris tells me to > mount zfs filesystems (1/9) and then works for 1-2 minutes until it goes > ahead. I hear the disk working but have no clue what happens here. > So I checked to zpool export and import, and with this import it is also > slow (takes around 90 seconds to import and with b97 it took 5 seconds). > Has anyone an idea what the reason could be ? > > I also had created 2 ZVOL''s under one filesysystem. Now I removed the > upper filesystem (and expected that zfs will also remove the both > zvols). But now on zpool exports it complains about these two unknown > datasets as: "dataset does not exist" > > Any comments and ideas how to "really" remove the zvols and what''s the > issue with slow zpool import ?maybe "zpool status" and "fmdump" can shed some light ... Michael -- Michael Schuster http://blogs.sun.com/recursion Recursion, n.: see ''Recursion''
Am 22.09.2008 um 17:22 schrieb Michael Schuster:> On 09/22/08 06:59, Detlef Drewanz at Sun.COM wrote: >> With Nevada Build 98 I realize a slow zpool import of my pool which >> holds my user and archive data on my laptop. >> The first time it was realized during the boot if Solaris tells me >> to mount zfs filesystems (1/9) and then works for 1-2 minutes until >> it goes ahead. I hear the disk working but have no clue what >> happens here. >> So I checked to zpool export and import, and with this import it is >> also slow (takes around 90 seconds to import and with b97 it took 5 >> seconds). Has anyone an idea what the reason could be ? >> I also had created 2 ZVOL''s under one filesysystem. Now I removed >> the upper filesystem (and expected that zfs will also remove the >> both zvols). But now on zpool exports it complains about these two >> unknown datasets as: "dataset does not exist" >> Any comments and ideas how to "really" remove the zvols and what''s >> the issue with slow zpool import ? > > maybe "zpool status" and "fmdump" can shed some light ...zpool status shows "No known data errors" and fmdump tells me "fltlog is empty". I also checked /var/adm/messages. But this all gives no idea. Any more ideas, where to look. Detlef
Hi Detlef, I have no problems with build 98. But the question about how many snapshots you have is a good one... I just booted a thumper with thousands of snapshots and it took me over an hour. Don''t you have snapshots of the boot environment? Kind regards Lars -- This message posted from opensolaris.org
On Mon, Sep 22, 2008 at 3:59 PM, Detlef Drewanz at Sun.COM < Detlef.Drewanz at sun.com> wrote:> With Nevada Build 98 I realize a slow zpool import of my pool which > holds my user and archive data on my laptop. > > The first time it was realized during the boot if Solaris tells me to > mount zfs filesystems (1/9) and then works for 1-2 minutes until it goes > ahead. I hear the disk working but have no clue what happens here. > So I checked to zpool export and import, and with this import it is also > slow (takes around 90 seconds to import and with b97 it took 5 seconds). > Has anyone an idea what the reason could be ? >You don''t by any chance have lots of USB flash storage devices or any blank media in the CD / DVD drive? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20080925/0e666201/attachment.html>
Hi again... today I maybe had the same problem you described... I had an on disk format of 11. After upgrading to 13 all works fine. -- This message posted from opensolaris.org
I''m also seeing a very slow import on the 2008.11 build 98 prerelease. I have the following setup: a striped zpool of 2 mirrors, both mirrors have 1 local disk and 1 iscsi disk. I was testing a setup with iscsiboot (windows vista) with gpxeboot, every client was booted from a iscsi exposed zvol, I had a lot of snapshots, I enabled the automatic snapshot service last week, I configured it to create a snapshot every 15min , And I kept all snapshots, Today (after 4days) my first server crashed, I''m right now importing the pool on my second node to test failover, but the import is alredy running for more then 45min :-( If I had know it took that much time, I should have configured to remove ol snapshots. K -- This message posted from opensolaris.org
I''m also seeing a slow import on the 2008.11 build 98 prerelease. but my situation is a little different : I have the following setup: a striped zpool of 2 mirrors, both mirrors have 1 local disk and 1 iscsi disk. I was testing iscsiboot (windows vista) with gpxeboot, every client was booted from a iscsi exposed zvol, and was connected via cifs to 1 zfs filesystem I had a lot of snapshots, I enabled the automatic snapshot service last week, I configured it to create a snapshot every 15min for every zvol and zfs filesystem , And I configured it to keep all snapshots. Today (after running well for 4days) my first server crashed, I''m right now importing the pool on my second node to test failover, but the import is already running for more then 45min :-( So keeping all those snapshots is a "dangerous" situation since it takes so much time to import the zpool on a another node. K -- This message posted from opensolaris.org