On Thu, Jun 17, 2010 at 20:39, Valerie Aurora <vaurora@redhat.com> wrote:
quoted text
> On Thu, Jun 17, 2010 at 10:01:30AM +0200, Alex Riesen wrote:
>> On Tue, Jun 15, 2010 at 20:39, Valerie Aurora <vaurora@redhat.com> wrote:
>> > +git://git.kernel.org/pub/scm/fs/ext2/val/e2fsprogs.git
>> > +
>> > +Currently, whiteout directory entries are not returned to userland.
>> > +While the directory type for whiteouts, DT_WHT, has been defined for
>> > +many years, very little userland code handles them. ??Userland will
>> > +never see fallthru directory entries.
>>
>> This may be a dumb question (I must admit I did only very little research),
>> but how does one cleanup the topmost layer of whiteouts and fallthroughs,
>> so that the entries of lower layer(s) can be made visible again?
>
> I'm not sure how best to do this.  We don't want to add more system
> calls.  One thought of mine has been to do this offline, when the file
> system is unmounted.

But that means that if the topmost filesystem is getting full of whiteouts
and fallthroughs there will be no way to free up the space without taking
the volume offline! That makes operation of union mount on always-on
systems difficult. Many personal electronics are always-on today, it
will be annoying to have to shutdown them on reconfigurations or just
to free up some space.

quoted text
> ... For example, e2fsck could add a feature to
> delete whiteouts and fallthrus. ...

That makes me think that the cleanup operation will be topmost
filesystem specific. Maybe this even means that one have to
have the filesystem specific tools installed on every system
which happens to use union mounts.

quoted text
> Another option is to add a flag to an existing system call.

Or calls, if the whiteouts (or even fallthroughs) are to be read
through directory file handles. unlinkat(2) ? It already has
dirfd and flags arguments.
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/