Processing commands for cont...@bugs.debian.org:
> tag 566072 + patch
Bug #566072 [util-linux] fsck now failing hard for unavailable filesystems
Ignoring request to alter tags of bug #566072 to the same tags previously set
> thanks
Stopping processing here.
Please contact me if you need assistanc
tag 566072 + patch
thanks
On Fri, 14 Jan 2011 20:48:38 +, Adam D. Barratt wrote:
> This appears to be due to the fact that the package build only invokes
> dh_installdebconf in the binary-indep target. As a result the templates
> file intended to warn you about the contents of your fstab is
reopen 566072
thanks
On Fri, 2011-01-14 at 21:13 +0100, Carsten Otto wrote:
> the patch introduced in #68 causes the postinst script to fail when
> upgrading from lenny to squeeze while the fstab contains a noauto entry
> with non-zero pass number.
>
> By adding -ex to the postinst script I got:
Processing commands for cont...@bugs.debian.org:
> reopen 566072
Bug #566072 {Done: LaMont Jones } [util-linux] fsck now
failing hard for unavailable filesystems
'reopen' may be inappropriate when a bug has been closed with a version;
you may need to use 'found' to remove fixed versions.
> thanks
Dear all,
the patch introduced in #68 causes the postinst script to fail when
upgrading from lenny to squeeze while the fstab contains a noauto entry
with non-zero pass number.
By adding -ex to the postinst script I got:
+ db_input critical util-linux/noauto-with-nonzero-passnum
+ _db_cmd 'INPUT
On 11/11/2010 09:02 PM, LaMont Jones wrote:
On Sun, Jan 31, 2010 at 06:58:21PM -0600, John Goerzen wrote:
Clint Adams wrote:
Is there a legitimate reason to set a pass number if you actually do not want
the filesystem to be checked?
I would say probably not. But in the past, I (and others) wo
On Sun, Jan 31, 2010 at 06:58:21PM -0600, John Goerzen wrote:
> Clint Adams wrote:
> >Is there a legitimate reason to set a pass number if you actually do not want
> >the filesystem to be checked?
> I would say probably not. But in the past, I (and others) would
> often cut-and-paste fstab lines,
Hi.
On Wed, Jan 20, 2010 at 04:44:46PM -0600, John Goerzen wrote:
>
> Better yet, it
> should never attempt to fsck a noauto filesystem. If it really must,
> an error to do so ought not be fatal to the boot process.
>
I have experienced the same kind of problem.
May I suggest also that fsck d
Clint Adams wrote:
On Wed, Jan 20, 2010 at 04:44:46PM -0600, John Goerzen wrote:
On a lark, I changed the pass number in fstab to 0. That fixed the
issue.
Is there a legitimate reason to set a pass number if you actually do not want
the filesystem to be checked?
I would say probably not.
On Wed, Jan 20, 2010 at 04:44:46PM -0600, John Goerzen wrote:
> On a lark, I changed the pass number in fstab to 0. That fixed the
> issue.
Is there a legitimate reason to set a pass number if you actually do not want
the filesystem to be checked?
--
To UNSUBSCRIBE, email to debian-bugs-rc-re
Package: util-linux
Version: 2.16.2-0
Severity: critical
Justification: breaks the whole system
The behavior I describe started after a recent sid upgrade on at least
three distinct systems.
Follows is my retyping the information that appears on the console on
one of them:
Checking file systems.
11 matches
Mail list logo
