• 0 Posts
  • 109 Comments
Joined 2 months ago
cake
Cake day: June 5th, 2025

help-circle










  • Yeah we have a camera pointed at our driveway from our garage door. It isn’t close enough to the road to trigger movement from people walking or driving by.

    But if they come inside the fence it’ll pick em up.

    Also have a couple of cameras watching other random parts of the yard. We live on just under 2 acres, and it’s all enclosed in chain link fencing. Next to us is an automotive maintenance shop owned by a buy here pay here lot a few miles closer to town, and they don’t always hire the most trustworthy individuals to work on cars…










  • You sure that’s what is happening, and it’s not just mounting a different snapshot/dataset being mounted “on top” ?

    I’ve seen it happen, which is why I ask. Assume the root dataset is named pool0 and has set0 set1 and set1/set2 as child datasets.

    Their mount points are as follows:

    /pool0/set0

    /pool0/set1

    /pool0/set1/set2

    Now, if somehow, say set2 gets unmounted.temporarily, and you save files to /pool0/set1/set2 while the data set is not mounted, it’ll actually put those files in the set1 dataset, under the set2 directory.

    But, when you mount the pool0/set1/set2 dataset again, the files under the set1 dataset are hidden by the set2 child.

    Am I explaining it well enough for you to follow along?

    Make sure you don’t have some similar situation by temporarily unmounting any nested datasets and ls’ing their mount points.