Your message dated Tue, 31 Dec 2013 20:27:31 -0500 with message-id <[email protected]> and subject line Re: missing lost+found should only result in a warning has caused the Debian Bug report #356698, regarding missing lost+found should only result in a warning to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 356698: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=356698 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: e2fsprogs Version: 1.38+1.39-WIP-2005.12.31-1 Severity: minor File: /sbin/e2fsck Hi, a missing /lost+found should only result in a warning, not an error. If the admin removes the file, he probably knows what he's doing and does not want the e2fsck to halt just because of that. Thanks, Joachim -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-rc6.otto Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Versions of packages e2fsprogs depends on: ii e2fslibs 1.38+1.39-WIP-2005.12.31-1 ext2 filesystem libraries ii libblkid1 1.38+1.39-WIP-2005.12.31-1 block device id library ii libc6 2.3.6-3 GNU C Library: Shared libraries an ii libcomerr2 1.38+1.39-WIP-2005.12.31-1 common error description library ii libss2 1.38+1.39-WIP-2005.12.31-1 command-line interface parsing lib ii libuuid1 1.38+1.39-WIP-2005.12.31-1 universally unique id library e2fsprogs recommends no packages. -- no debconf information
--- End Message ---
--- Begin Message ---tags 356698 wontfix thanks A missing lost+found directory can result in data losee if there is an orphaned inode and e2fsck can find no place to put the disconnected (i.e., orphaned) inode. Allowing this without risking data loss in a number of corner cases in the case of a corrupted file system is just way too much complexity. Sorry. - Ted
--- End Message ---
