Bug 123574 - [unionfs] df(1) -t option destroys info for unionfs (and maybe other) mounts
Summary: [unionfs] df(1) -t option destroys info for unionfs (and maybe other) mounts
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: 6.3-RELEASE
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-10 20:00 UTC by Chad Milios
Modified: 2017-12-31 22:27 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chad Milios 2008-05-10 20:00:12 UTC
df alone shows info for each layering of a unionfs mount. when using
the -t option, all layers show the info pertaining to only the top layer.

levar# df -h
Filesystem                      Size    Used   Avail Capacity  Mounted on
/dev/mirror/levar               3.9G    368M    3.2G    10%    /
devfs                           1.0K    1.0K      0B   100%    /dev
/dev/concat/cbus                 77G     15G     56G    21%    /media/cbus
/media/cbus/levar/var            77G     15G     56G    21%    /var
/media/cbus/levar/usr/src        77G     15G     56G    21%    /usr/src
/media/cbus/levar/usr/obj        77G     15G     56G    21%    /usr/obj
/media/cbus/levar/usr/ports      77G     15G     56G    21%    /usr/ports
/media/cbus/levar/home           77G     15G     56G    21%    /home
/dev/ufs/ttown                  389G    387G    1.9G   100%    /media/ttown
/dev/ufs/sly                    389G    291G     98G    75%    /media/sly
/dev/ufs/pburg                  389G    137G    252G    35%    /media/pburg
/dev/ufs/kron                   389G    377G     12G    97%    /media/kron
<above>:/media/ttown/Archive    467G    465G    1.9G   100%    /home/joe/Archive
<above>:/media/kron/Archive     856G    843G     12G    99%    /home/joe/Archive
<above>:/media/pburg/Archive    1.2T    993G    252G    80%    /home/joe/Archive
<above>:/media/sly/Archive      1.6T    1.5T     98G    94%    /home/joe/Archive

levar# df -ht nofoobarfs
Filesystem                     Size    Used   Avail Capacity  Mounted on
/dev/mirror/levar              3.9G    368M    3.2G    10%    /
devfs                          1.0K    1.0K      0B   100%    /dev
/dev/concat/cbus                77G     15G     56G    21%    /media/cbus
/media/cbus/levar/var           77G     15G     56G    21%    /var
/media/cbus/levar/usr/src       77G     15G     56G    21%    /usr/src
/media/cbus/levar/usr/obj       77G     15G     56G    21%    /usr/obj
/media/cbus/levar/usr/ports     77G     15G     56G    21%    /usr/ports
/media/cbus/levar/home          77G     15G     56G    21%    /home
/dev/ufs/ttown                 389G    387G    1.9G   100%    /media/ttown
/dev/ufs/sly                   389G    291G     98G    75%    /media/sly
/dev/ufs/pburg                 389G    137G    252G    35%    /media/pburg
/dev/ufs/kron                  389G    377G     12G    97%    /media/kron
<above>:/media/sly/Archive     1.6T    1.5T     98G    94%    /home/joe/Archive
<above>:/media/sly/Archive     1.6T    1.5T     98G    94%    /home/joe/Archive
<above>:/media/sly/Archive     1.6T    1.5T     98G    94%    /home/joe/Archive
<above>:/media/sly/Archive     1.6T    1.5T     98G    94%    /home/joe/Archive

levar# df -ht unionfs
Filesystem                    Size    Used   Avail Capacity  Mounted on
<above>:/media/sly/Archive    1.6T    1.5T     98G    94%    /home/joe/Archive
<above>:/media/sly/Archive    1.6T    1.5T     98G    94%    /home/joe/Archive
<above>:/media/sly/Archive    1.6T    1.5T     98G    94%    /home/joe/Archive
<above>:/media/sly/Archive    1.6T    1.5T     98G    94%    /home/joe/Archive

How-To-Repeat: create some unionfs mount points, and run `df` and `df -t nofoobarfs`
and `df -t unionfs` and check the output.

here are the pertinent lines in my fstab:

/media/ttown/Archive    /home/joe/Archive       unionfs rw,noatime,copymode=transparent,late    0       0
/media/kron/Archive     /home/joe/Archive       unionfs rw,noatime,copymode=transparent,late    0       0
/media/pburg/Archive    /home/joe/Archive       unionfs rw,noatime,copymode=transparent,late    0       0
/media/sly/Archive      /home/joe/Archive       unionfs rw,noatime,copymode=transparent,late    0       0

here are all the rest, if for some reason some of the properties of the
encompassing mount points seem to have an effect:

/dev/mirror/levar       /       ufs     rw,noatime      1       1
/dev/concat/cbus        /media/cbus     ufs     rw,noatime      1       2
/dev/ufs/ttown  /media/ttown    ufs     rw,noatime,late 1       2
/dev/ufs/sly    /media/sly      ufs     rw,noatime,late 1       2
/dev/ufs/pburg  /media/pburg    ufs     rw,noatime,late 1       2
/dev/ufs/kron   /media/kron     ufs     rw,noatime,late 1       2
/media/cbus/levar/var   /var    nullfs  rw,noatime      0       0
/media/cbus/levar/usr/src       /usr/src        nullfs  rw,noatime      0       0
/media/cbus/levar/usr/obj       /usr/obj        nullfs  rw,noatime      0       0
/media/cbus/levar/usr/ports     /usr/ports      nullfs  rw,noatime      0       0
/media/cbus/levar/home  /home   nullfs  rw,noatime      0       0
Comment 1 Matteo Riondato freebsd_committer freebsd_triage 2008-05-17 10:01:35 UTC
Responsible Changed
From-To: freebsd-bugs->daichi

User is running 6.3 which, IIRC, does not include the new unionfs implementation, but this 
bug may be present in the new one too. Daichi surely knows whether this is the case.
Comment 2 Mark Linimon freebsd_committer freebsd_triage 2013-07-03 01:50:32 UTC
State Changed
From-To: open->open

commit bit has been taken in for safekeeping. 


Comment 3 Mark Linimon freebsd_committer freebsd_triage 2013-07-03 01:50:32 UTC
Responsible Changed
From-To: daichi->freebsd-fs
Comment 4 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 08:00:52 UTC
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped