On Tue, Oct 14, 2014 at 9:45 PM, Steven Hartland via illumos-zfs <
z...@lists.illumos.org> wrote:
>
> - Original Message - From: "Steven Hartland"
>
>> I've been investigating an issue for a user who was seeing
>> his pool import hang after upgrading on FreeBSD. After
>> digging around it
On Tue, Oct 14, 2014 at 9:45 PM, Steven Hartland via illumos-zfs <
z...@lists.illumos.org> wrote:
>
> - Original Message - From: "Steven Hartland"
>
>> I've been investigating an issue for a user who was seeing
>> his pool import hang after upgrading on FreeBSD. After
>> digging around it
- Original Message -
From: "Steven Hartland"
I've been investigating an issue for a user who was seeing
his pool import hang after upgrading on FreeBSD. After
digging around it turned out the issue was due to lack
of free space on the pool.
As the pool imports it writes hence requirin
So, the commit you referenced is the commit that introduced the
behavior of "in these error cases, we can't figure out what's in use
reliably, so 'leak the space', log that we leaked it, and that way we
don't corrupt things at the cost of space".
So I would posit that the problem may be one of a l
> On Oct. 6, 2014, 11:31 p.m., Bayard Bell wrote:
> > I'm a bit uncomfortable with the level of bug reporting and fix analysis
> > here. The changes would seem sufficient to preventing panic in this case of
> > import failure, but what's not clear is how we expect this to be handled
> > therea
> On Oct. 6, 2014, 11:31 p.m., Bayard Bell wrote:
> > I'm a bit uncomfortable with the level of bug reporting and fix analysis
> > here. The changes would seem sufficient to preventing panic in this case of
> > import failure, but what's not clear is how we expect this to be handled
> > therea
> On Oct. 6, 2014, 11:31 p.m., Bayard Bell wrote:
> > I'm a bit uncomfortable with the level of bug reporting and fix analysis
> > here. The changes would seem sufficient to preventing panic in this case of
> > import failure, but what's not clear is how we expect this to be handled
> > therea
I've been investigating an issue for a user who was seeing
his pool import hang after upgrading on FreeBSD. After
digging around it turned out the issue was due to lack
of free space on the pool.
As the pool imports it writes hence requiring space but the
pool has so little space this was failing
