| Summary: | Changed df behavior with overlapping mounts | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Frank Griffin <ftg> |
| Component: | RPM Packages | Assignee: | Base system maintainers <basesystem> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | marja11, pterjan |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | coreutils | CVE: | |
| Status comment: | |||
|
Description
Frank Griffin
2015-07-13 17:15:57 CEST
@ Frank Sorry for the very late reply. As you know, BugSquad is short on active members. Tbh, I'd never thought having overlapping mounts would be possible at all, regardless of on which side they overlap. Is it not possible or better to have only ftgme2:/data /mnt/ftgme2.data nfs rw,bg,soft 0 0 and link /home/ftg/.thunderbird to /mnt/ftgme2.data/ftg/.thunderbird ? Assigning to the basesystem maintainers, assuming this issue is still valid, please close this ticket if it isn't! CC:
(none) =>
marja11 IIRC df behaviour depends if you have /etc/mtab but I don't remember the details If also has some duplicate detection code. I thought it was keeping the shortest one but not sure, and it has changed over the years. Looking at http://git.savannah.gnu.org/cgit/coreutils.git/plain/NEWS * Noteworthy changes in release 8.25 (2016-01-20) [stable] df now prefers sources towards the root of a device when eliding duplicate bind mounted entries. Which may be related. CC:
(none) =>
pterjan Also, * Noteworthy changes in release 8.24 (2015-07-03) [stable] df no longer suppresses separate exports of the same remote device, as these are generally explicitly mounted. The --total option does still suppress duplicate remote file systems. [suppression was introduced in coreutils-8.21] So, can you try in cauldron? It seems it was fixed upstream by the release which happened 10 days before you reported this bug last year, and we have a more recent one now. Working now. Status:
NEW =>
RESOLVED |