Your message dated Mon, 11 Feb 2008 12:44:45 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#465211: Not every fsck.something has a -p flag
has caused the Debian Bug report #465211,
regarding Not every fsck.something has a -p flag
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.)
--
465211: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=465211
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: fsck
Version: 1.39+1.40-WIP-2006.11.14+dfsg-2etch1
The "fsck" command for some filesystems (at least for ocfs2) lacks a "-
p" parameter, thus checking of these filesystems fails when calling
"fsck -Aa".
When checking filesystems at boot time, check fails forcing the system
into single-user mode which is really inconvenient
From /var/log/fsck/checkfs , generated by /etc/init.d/checkfs from
package initscripts:
<--- cut here --->
Log of fsck -C -R -A -a
Mon Feb 11 10:24:04 2008
fsck.ocfs2: invalid option -- a
Usage: fsck.ocfs2 [ -fGnuvVy ] [ -b superblock block ]
[ -B block size ] device
Critical flags for emergency repair:
-n Check but don't change the file system
-y Answer 'yes' to all repair questions
-f Force checking even if file system is clean
-F Ignore cluster locking (dangerous!)
Less critical flags:
-b superblock Treat given block as the super block
-B blocksize Force the given block size
-G Ask to fix mismatched inode generations
-u Access the device with buffering
-V Output fsck.ocfs2's version
-v Provide verbose debugging output
fsck died with exit status 16
Mon Feb 11 10:24:04 2008
----------------
<--- cut here --->
Should this be fixed in the fsck command of the e2fsprogs? Or should I
report to the maintainers of fsck.ocfs2? Or the maintainers of
initscripts?
Thanks in advance
--
Luis Gómez
INCIDE - Investigación Digital, S.L.
--- End Message ---
--- Begin Message ---
This is a dupe (due to resubmission) of bug #465216.
- Ted
--- End Message ---
