Date: Mon, 13 Oct 2014 22:56:48 +0100 From: "Steven Hartland" <killing@multiplay.co.uk> To: "mark" <Mark.Martinec@ijs.si>, <freebsd-fs@freebsd.org>, <freebsd-stable@freebsd.org> Cc: FreeBSD Stable <freebsd-stable@freebsd.org> Subject: Re: zpool import hangs when out of space - Was: zfs pool import hangs on [tx->tx_sync_done_cv] Message-ID: <E3C3C359999140B48943A0E1A04F83A9@multiplay.co.uk> References: <54372173.1010100@ijs.si> <644FA8299BF848E599B82D2C2C298EA7@multiplay.co.uk> <54372EBA.1000908@ijs.si> <DE7DD7A94E9B4F1FBB3AFF57EDB47C67@multiplay.co.uk> <543731F3.8090701@ijs.si> <543AE740.7000808@ijs.si> <A5BA41116A7F4B23A9C9E469C4146B99@multiplay.co.uk> <CAHM0Q_N%2BC=3qgUnyDkEugOFcL=J8gBjbTg8v45Vz3uT=e=Fn2g@mail.gmail.com> <6E01BBEDA9984CCDA14F290D26A8E14D@multiplay.co.uk> <CAHM0Q_OpV2sAQQAH6Cj_=yJWAOt8pTPWQ-m45JSiXDpBwT6WTA@mail.gmail.com> <E2E24A91B8B04C2DBBBC7E029A12BD05@multiplay.co.uk> <CAHM0Q_Oeka25-kdSDRC2evS1R8wuQ0_XgbcdZCjS09aXJ9_WWQ@mail.gmail.com> <14ADE02801754E028D9A0EAB4A16527E@multiplay.co.uk> <543C3C47.4010208@ijs.si>
next in thread | previous in thread | raw e-mail | index | archive | help
----- Original Message -----
From: "mark" <Mark.Martinec@ijs.si>
To: <freebsd-fs@freebsd.org>; <freebsd-stable@freebsd.org>
Cc: "FreeBSD Stable" <freebsd-stable@freebsd.org>
Sent: Monday, October 13, 2014 9:55 PM
Subject: Re: zpool import hangs when out of space - Was: zfs pool import hangs on [tx->tx_sync_done_cv]
> On 10/13/2014 22:10, Steven Hartland wrote:
>> So the issue is simply the pool is out of space to perform the import
>> as that process, when not readonly, requires space to write to the pool.
>>
>> The problem with that is that during this process it has the pool lock so
>> any subsequent zpool actions are dead in the water as they will block
>> waiting on that lock.
>>
>> Something to discuss with the openzfs guys, but I would say the import
>> should fail with a no space error.
>>
>> So Mark the mystery is solved, when you upgraded you ran the pool so low
>> on space that it now can't be imported RW as that requires a write.
>>
>> Regards
>> Steve
>
> Thank you both for analysis and effort!
>
> I can't rule out the possibility that my main system pool
> on a SSD was low on space at some point in time, but the
> three 4 GiB cloned pools (sys1boot and its brothers) were all
> created as a zfs send / receive copies of the main / (root)
> file system and I haven't noticed anything unusual during
> syncing. This syncing was done manually (using zxfer) and
> independently from the upgrade on the system - on a steady/quiet
> system, when the source file system definitely had sufficient
> free space.
>
> The source file system now shows 1.2 GiB of usage shown
> by df:
> shiny/ROOT 61758388 1271620 60486768 2% /
> Seems unlikely that the 1.2 GiB has grown to 4 GiB space
> on a cloned filesystem.
>
> Will try to import the main two pools after re-creating
> a sane boot pool...
Yer zfs list only shows around 2-3GB used too but zpool list
shows the pool is out of space. Cant rule out an accounting
issue though.
Regards
Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E3C3C359999140B48943A0E1A04F83A9>