I also vote that
[options]
allow_cancellation = true
should be added to /etc/e2fsck.conf in default Ubuntu installations.
I've changed the status from "Fix Released" to "Confirmed" in order to
signal the Ubuntu developers that there are several votes requesting
this.
** Changed in: sysv
I consent to that. It is possible to skip fsck when using splash, but is
not when not using splash.
If that feature is implemented in usplash it seems to be consens in the
community that it is necessary. And if that is the case, users not
utilizing usplash should not be excluded...
--
Should be
[quoting spaceman]
basicly:
See man e2fsck.conf(5). Create a file /etc/e2fsck.conf, with the
contents:
[options]
allow_cancellation = true
Then you should be able to type ^C while it is doing a check, and cancel
the fsck.
I vote this should be the default
[/quote]
I second this.
Three
YES! I can cancel now
after reading this:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg251597.html
basicly:
See man e2fsck.conf(5). Create a file /etc/e2fsck.conf, with the
contents:
[options]
allow_cancellation = true
Then you should be able to type ^C while it is doing a check,
Hmmm it's another bug that needs another report. I haven't looked for it
but i think someone must have reported it already.
--
Should be warned of upcoming forced fsck
https://bugs.launchpad.net/bugs/22460
You received this bug notification because you are a member of Ubuntu
Bugs, which is a dire
This is welcome news and I appreciate the effort. However, so far I
haven't had much luck. Pressing esc to skip causes the boot process to
freeze and need a reboot. Of course I haven't seen the option in several
days so maybe it's been fixed.
--
Should be warned of upcoming forced fsck
https://bu
The forced check is integrated in the splash screen in Hardy and it is
possible to skip it.
** Changed in: sysvinit (Ubuntu)
Status: Confirmed => Fix Released
--
Should be warned of upcoming forced fsck
https://bugs.launchpad.net/bugs/22460
You received this bug notification because you a
** Also affects: sysvinit (Baltix)
Importance: Undecided
Status: New
--
Should be warned of upcoming forced fsck
https://bugs.launchpad.net/bugs/22460
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
but it would be - indeed - a good idea to implement it. It seems to me
that this is an issue for many people. And I think solving this is
important for making ubuntu presentable to the broad mass and therefore
fixing bug #1.
--
Should be warned of upcoming forced fsck
https://bugs.launchpad.net/b
Try AutoFsck:
http://wiki.ubuntu.com/AutoFsck
It basically moves this automated 'just in case' check to shutdown and
gives you the option not to run it if it's a bad time. There's also a
nice simple script (with zenity GUI) on that page which allows you to
easily change the interval.
--
Should
A value of "0" for the check interval disables the checks.
Something like "tune2fs -c 0 /dev/sda" should disable checks based on mount
counts; then is is a matter of "tune2fs -i 1m /dev/sda" to check /dev/sda each
month.
--
Should be warned of upcoming forced fsck
https://bugs.launchpad.net/bug
Isn't the forced check already based on time or number of mounts
(whichever comes first)? Anyway `tune2fs -i` seems to set the max time
between forced mounts.
--
Should be warned of upcoming forced fsck
https://bugs.launchpad.net/bugs/22460
You received this bug notification because you are a mem
Regarding the check-on-shut-down:
It is an interesting idea, but care should be taken in special cases such as
UPS initiated shut-down or low battery laptops - it would be awful to lose
power in the middle of a fsck.
Another idea would be to have a time-based forced fsck. This should be
benefici
Hi
Fist at all i sow about 4-5 bug reported around de fsck on booting stage.
My point is why fsck dont care of what i set with tune2fs?
This is the way I chose to run or not on booting process.
I sow some 1 propose to wait 10s and give you a choise to stop him pressing
CTRL-C or CTRL-D my question
Well, I used the installation CD to run Ubuntu, modified /etc/fstab/ so
it won't run again. Anyway, there shoud be a easier way to cancel fsck.
--
Should be warned of upcoming forced fsck
https://bugs.launchpad.net/bugs/22460
You received this bug notification because you are a member of Ubuntu
B
My laptop just hangs while doing the check, and i can not cancel it, so
i have no access to my data. There MUST be a way to cancel fsck, it's
absolutely necesary. Is not only a matter of wasting time or batery, if
disk check fails the computer is totally unaccessible.
--
Should be warned of upcom
Another issues that it doesn't check consistently after 30 mounts. In
fact, it varies all over the place. Today, mine ran after 21 mounts and
it's a fresh install at that. Is there a reason 30 doesn't mean 30? If
it's going to run when it feels like it, we definitely need the ability
to postpone it
[cross-posted from bug #3581, which is similar]
In my opinion, the best solution is to make fsck run on *shutdown*
rather than on boot-up. The rationale behind this is that people usually
turn on their computers to do something with it. At those times, people
want their computers to boot up as fas
I also would like to be able to either cancel/skip the disk check on
boot, or the best option would be to ask users if the disk check can be
performed on shutdown, although I know that would require significant
changes. Giving users a yes/no choice before performing the disk check
is an easy fix,
As far as I can see from the corresponding scripts
/etc/init.d/checkfs.sh and /etc/init.d/checkroot.sh a check if the
system is running on battery is already done.
Also these scripts could be easily modified to give the user something like a
10 second delay to cancel the check, and start it other
The forced fsck is really annoying, and dropping back to text mode and
not being able to easily stop the check makes it worse. I like Huygens
suggestions and would formulate it as this:
Short-term fix:
- don't do the check if laptop runs on battery
- make it easier to cancel a check
- make it poss
@Jim
It seems also at first thought better from my usage point of view to have the
scan at shutdown. Because, I usually shut down my computer and go doing other
things without looking at it.
However, the "shutdown" phase is also used upon reboot (at least, I do not know
if the scripts executed u
Bonager (mentioned above) is great workaround for this "bug" but a fix
that gave users more control would be nice. In fact, we should be
allowed to choose to run the scan on boot up or shut down. Most of the
time, I'd rather it run on shut down because I'm done and don't care if
it runs a check but
What is the status of this item?
Importance is now listed as wishlist, but I think that according to the posts
above and the conducted poll on the forum this is an important issue for many
of us.
Just a small message on how to cancel the current check would make things a lot
better, but more wor
There is a program that does what the original author of this bug
wanted: "I'd much rather that on the 29th boot, you got a message after
logging in warning you about this, and also giving you an option to run
the check at any point in the current session." The program is called
Bonager: The Boot S
Reopening, as this is not a duplicate of 3851 and has not been resolved.
** Changed in: sysvinit (Ubuntu)
Status: Rejected => Confirmed
--
Should be warned of upcoming forced fsck
https://launchpad.net/bugs/22460
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubu
A forced disk check every thirty boots is quite bad for users with 750GB
drives. The check takes an extremely long time. Users may believe
their system to be broken.
The check itself is essential, but the current behavior should be easy
to discover and easy to modify.
--
Should be warned of up
27 matches
Mail list logo
