Bug#579640: lost+found check triggers on bind-mounted subdir
On Fri, Mar 23, 2012 at 08:43:40AM +0100, Raphael Hertzog wrote: I'm not sure why you insist in keeping that feature working while it has been said that the recovery tools do create the needed directories by themselves. We are planning on removing it, just not gotten around to do it yet. Anyway, when can we see a fix for this? Soon or when time permits I'm raising the severity because it would be nice to see it fixed for wheezy. I'm sure we can get it fixed before then. Regards Javier signature.asc Description: Digital signature
Bug#579640: lost+found check triggers on bind-mounted subdir
severity 579640 important thanks On Mon, 30 Jan 2012, Christian Kastner wrote: On 2012-01-30 17:54, Kari Pahula wrote: On Fri, Jan 20, 2012 at 08:21:00PM +0100, Javier Fernández-Sanguino Peña wrote: On Fri, Jan 20, 2012 at 10:49:21AM +0100, Christian Kastner wrote: with /etc/mtab now being a symlink to /proc/mounts (which doesn't store information about bind mounts), I believe we will have to disable this check altogether. Maybe we have to, but if that information is no longer readily available I would think this is an undesired behaviour. Where can one determine now if a mounted filesystem uses a bind mount? /proc/self/mountinfo Well, indeed! I guess I was fixated on seeing the bind option somewhere, and a search was unsuccessful. This looks fine, though. I'm not sure why you insist in keeping that feature working while it has been said that the recovery tools do create the needed directories by themselves. Anyway, when can we see a fix for this? At the very least, you should disable the check by default... because it's too likely that users will get annoyed and the number of comments and people reopening that bug make it obvious that this is the case. I'm raising the severity because it would be nice to see it fixed for wheezy. Thank you for your work on this core package! Cheers, -- Raphaël Hertzog ◈ Debian Developer Pre-order a copy of the Debian Administrator's Handbook and help liberate it: http://debian-handbook.info/liberation/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#579640: lost+found check triggers on bind-mounted subdir
On Fri, Jan 20, 2012 at 08:21:00PM +0100, Javier Fernández-Sanguino Peña wrote: On Fri, Jan 20, 2012 at 10:49:21AM +0100, Christian Kastner wrote: with /etc/mtab now being a symlink to /proc/mounts (which doesn't store information about bind mounts), I believe we will have to disable this check altogether. Maybe we have to, but if that information is no longer readily available I would think this is an undesired behaviour. Where can one determine now if a mounted filesystem uses a bind mount? /proc/self/mountinfo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#579640: lost+found check triggers on bind-mounted subdir
On 2012-01-30 17:54, Kari Pahula wrote: On Fri, Jan 20, 2012 at 08:21:00PM +0100, Javier Fernández-Sanguino Peña wrote: On Fri, Jan 20, 2012 at 10:49:21AM +0100, Christian Kastner wrote: with /etc/mtab now being a symlink to /proc/mounts (which doesn't store information about bind mounts), I believe we will have to disable this check altogether. Maybe we have to, but if that information is no longer readily available I would think this is an undesired behaviour. Where can one determine now if a mounted filesystem uses a bind mount? /proc/self/mountinfo Well, indeed! I guess I was fixated on seeing the bind option somewhere, and a search was unsuccessful. This looks fine, though. Thanks, Christian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#579640: lost+found check triggers on bind-mounted subdir
On 2012-01-20 20:21, Javier Fernández-Sanguino Peña wrote: On Fri, Jan 20, 2012 at 10:49:21AM +0100, Christian Kastner wrote: with /etc/mtab now being a symlink to /proc/mounts (which doesn't store information about bind mounts), I believe we will have to disable this check altogether. Maybe we have to, but if that information is no longer readily available I would think this is an undesired behaviour. Where can one determine now if a mounted filesystem uses a bind mount? From what I checked, nowhere -- hence why I think we have to disable it; it's unfixable. This was also the reason why we switched grabbing the mount information from the mount(8) to /etc/mtab in -117 (to close #578856); /etc/mtab was the only place that stored this kind of information. Regards, Christian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#579640: lost+found check triggers on bind-mounted subdir
Hi, On 2012-01-16 22:13, Flavio Stanchina wrote: I upgraded cron yesterday and I now received this warning: The following lost+found directories were not available: /srv/lost+found Here, /srv is a bind mount of a subdirectory in another filesystem, so it's perfectly normal that there isn't a lost+found directory there. I'm not going to argue about the absolute usefulness of the test, as this has already been done extensively in previous discussion, and I have now disabled it, but I think this specific problem is worth fixing if at all possible. with /etc/mtab now being a symlink to /proc/mounts (which doesn't store information about bind mounts), I believe we will have to disable this check altogether. Christian signature.asc Description: OpenPGP digital signature
Bug#579640: lost+found check triggers on bind-mounted subdir
On Fri, Jan 20, 2012 at 10:49:21AM +0100, Christian Kastner wrote: with /etc/mtab now being a symlink to /proc/mounts (which doesn't store information about bind mounts), I believe we will have to disable this check altogether. Maybe we have to, but if that information is no longer readily available I would think this is an undesired behaviour. Where can one determine now if a mounted filesystem uses a bind mount? Regards Javier signature.asc Description: Digital signature
Bug#579640: lost+found check triggers on bind-mounted subdir
I upgraded cron yesterday and I now received this warning: The following lost+found directories were not available: /srv/lost+found Here, /srv is a bind mount of a subdirectory in another filesystem, so it's perfectly normal that there isn't a lost+found directory there. I'm not going to argue about the absolute usefulness of the test, as this has already been done extensively in previous discussion, and I have now disabled it, but I think this specific problem is worth fixing if at all possible. -- Ciao, Flavio Those who do not understand Unix are condemned to reinvent it, poorly. -- Henry Spencer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
