On Thu, Aug 19, 2010 at 09:11:39PM +0400, SIO wrote:
>
> Here is my /etc/e2fsck.conf:
> [options]
> allow_cancellation = true
>
> Though cancellation is allowed, when I hit ^c during check of my root
> partition
> at system boot, it is remounted as read-only. File system is not flagged as
> containing errors, check is triggered by mounts count.
>
> Steps to reproduce:
> 1. Add mentioned option to /etc/e2fsck.conf
> 2. Set mount count greater than max-mount-count for your fs: tune2fs -C 100
> /dev/sda1
> 3. Reboot
> 4. Hit ^c during filesystem check
Can you try testing this by running e2fsck /dev/sda1 by hand, typing
^C, and then checking the exit value? i.e:
<tytso.r...@tytso-glaptop> {/home/tytso}
2087# /tmp/sbin/e2fsck.static /dev/funarg/kbuild
e2fsck 1.41.12 (17-May-2010)
/dev/funarg/kbuild has been mounted 35 times without being checked, check
forced.
Pass 1: Checking inodes, blocks, and sizes
^C/dev/funarg/kbuild: e2fsck canceled.
<tytso.r...@tytso-glaptop> {/home/tytso}
2088# echo $?
0
I've tried replicating this with the e2fsck.static from the package
e2fsck-static_1.41.12-2_amd64.deb, and with the allow_cancellation
option set, I'm not able to replicate the problem. That is, when I
interrupt e2fsck, the exit code is properly zero.
I'm wondering if the problem is because of the fact that you are
interrupting the init script, which is then somehow exiting with a
non-zero status. If that's true, then it's not something that's under
the control of e2fsprogs. Hence my request for you to test this
without having the boot scripts involved. If it works w/o the boot
scripts, then the problem will be in the init scripts.
Best regards,
- Ted
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
