On Fri, Mar 16, 2012 at 3:06 PM, Brandon High <bh...@freaks.com> wrote:
> On Fri, Mar 16, 2012 at 2:35 PM, Philip Brown <p...@bolthole.com> wrote:
>> if there isnt a process visible doing this via ps, I'm wondering how
>> one might check if a zfs filesystem or snapshot is rendered "busy" in
>> this way, interfering with an unmount or destroy?
>> I'm also wondering if this sort of thing can mean interference between
>> some combination of multiple send/receives at the same time, on the
>> same filesystem?
> Look at 'zfs hold', 'zfs holds', and 'zfs release'. Sends and receives
> will place holds on snapshots to prevent them from being changed.
yup, know about holds. wasnt those.
The reason for my question is, I recently ran into a situation where
there was a single orphaned zfs filesystem, no snapshots (therefore no
holds), no subfilesystems, no clones... and as far as I'm aware, no
send or receive active for it.
There were a bunch before that time, but they had all completed, I believe.
so I'm trying to figure out if there was any kind of left-over lock,
and how I might see that.
Is there some "zdb" magic?
zfs-discuss mailing list