Skip to content

Commit 92d7dca

Browse files
author
phil
committed
Note error when FFS does not support whiteouts and how to fix. (PR 3233)
1 parent a27c943 commit 92d7dca

File tree

1 file changed

+12
-6
lines changed

1 file changed

+12
-6
lines changed

sbin/mount_union/mount_union.8

Lines changed: 12 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
.\" $NetBSD: mount_union.8,v 1.5 1996/01/15 02:00:21 thorpej Exp $
1+
.\" $NetBSD: mount_union.8,v 1.6 1997/06/30 20:06:39 phil Exp $
22
.\"
33
.\" Copyright (c) 1994
44
.\" The Regents of the University of California. All rights reserved.
@@ -182,15 +182,21 @@ accessible via
182182
.Xr unmount 2 ,
183183
.Xr fstab 5 ,
184184
.Xr mount 8 ,
185-
.Xr mount_null 8
185+
.Xr mount_null 8 ,
186+
.Xr fsck_ffs 8
186187
.Sh BUGS
187188
Without whiteout support from the filesystem backing the upper layer,
188189
there is no way that delete and rename operations on lower layer
189190
objects can be done.
190-
.Dv EROFS
191-
is returned for this kind of operations along with any others
192-
which would make modifications to the lower layer, such as
193-
.Xr chmod 1 .
191+
An attempt to mount a union directory under one which does not
192+
have whiteout support will return
193+
.Dv EOPNOTSUPP
194+
(``Operation not supported'').
195+
Whiteout support can be added to an existing FFS filesystem
196+
by using the
197+
.Fl c
198+
option of
199+
.Xr fsck_ffs 8 .
194200
.Pp
195201
Running
196202
.Xr find 1

0 commit comments

Comments
 (0)