This bug has been nominated for gutsy, but it seems unlikely that we're
going to see any SRU activity for it given that there's been a
subsequent Ubuntu release since then. Marking 'wontfix'.
** Changed in: e2fsprogs (Ubuntu Gutsy)
Status: New => Won't Fix
--
fsck on every (re)boot
https
Tim, Franziskus,
Its not clear that the problem you are seeing has the same root
cause as previous reports that have been against this bug database. Can
you send the full output of your fsck output?
This problem can be caused by a faulty CMOS clock, or the CMOS battery
being dead, such that
Hello,
I also have this buggy behaviour in 8.04 upgraded since Drapper.
Please fix this.
--
fsck on every (re)boot
https://bugs.launchpad.net/bugs/63175
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
I have Ubuntu Hardy installed since the Beta release and I have all the
updates. Since a week (or maybe two) fsck is checking my root partition
on every (re)boot and breaks also the usplash boot to textual boot.
If you need further information on that, please let me know how I may
help.
--
fsck
> Now that the buggy init scripts have been fixed in util-linux, I suggest
> people affected by this bug change buggy_init_scripts option to 0 in
> /etc/e2fsck.conf.
If you think further changes to e2fsprogs are needed, please open a
separate bug report for that. This bug report is milestoned as
Now that the buggy init scripts have been fixed in util-linux, I suggest
people affected by this bug change buggy_init_scripts option to 0 in
/etc/e2fsck.conf. If nothing comes up, it's probably a good idea to let
it default to 0. If util-linux does not initialize system time properly,
fix it, inst
There is an open question about whether e2fsprogs still needs to work
around the clock setting at fsck time because of a change that has now
been made to util-linux, but regardless, e2fsprogs 1.40.8 has been
merged into hardy now so I believe this bug is fixed.
If anyone is still seeing this behav
** Changed in: e2fsprogs (Ubuntu)
Target: ubuntu-8.04-beta => ubuntu-8.04
--
fsck on every (re)boot
https://bugs.launchpad.net/bugs/63175
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
Hi,
The changelog of util-linux 2.13-10ubuntu1 has
- deliver hwclockfirst.sh on ubuntu as well. LP: #63175
Theodore, does this address your problem with the init scripts,
or is it a Debian problem as well as an Ubuntu one?
This change is only in Hardy, so is anyone able to
reproduce there?
I too have almost the same problem. Im using alpha3 ubuntu 8.04 i386
version on amd64 laptop. It scare me to boot to linux as everytime its
going to do the fsck thing and some kind of error comes up
fsck 1.40.3 (05-Dec-2007)
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
There are differences between boot
** Changed in: e2fsprogs (Ubuntu)
Importance: Medium => High
Target: None => ubuntu-8.04-beta
--
fsck on every (re)boot
https://bugs.launchpad.net/bugs/63175
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
** Tags added: qa-hardy-platform
** Tags removed: qa-hardy-list
--
fsck on every (re)boot
https://bugs.launchpad.net/bugs/63175
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.
** Tags added: qa-hardy-list
--
fsck on every (re)boot
https://bugs.launchpad.net/bugs/63175
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman
Sorry theodore for that i didn't provide the information correctly. I am not
a Linux Expert :-(
On Dec 16, 2007 8:34 PM, Theodore Ts'o <[EMAIL PROTECTED]> wrote:
> Bulldog, this is due to Ubuntu having buggy init scripts, and not
> setting the time correctly before running e2fsck. For some numbe
Bulldog, this is due to Ubuntu having buggy init scripts, and not
setting the time correctly before running e2fsck. For some number of
strange reasons I haven't been able to get Ubuntu staff to deal with
this problem correclty, so starting with e2fsprogs 1.40.3, the
debian/rules files have been se
I experience this problem
Running e2fsprogs 1.40.2-1ubuntu1 (gutsy) and my hardware clock is
ticking localtime - at least it says LOCAL in /etc/adjtime
Timezone is Europe/London
--
fsck on every (re)boot
https://bugs.launchpad.net/bugs/63175
You received this bug notification because you are a
I am sorry I did not provide those details
Ubuntu 7.10
Esfsprogs version - 1.40.2-1ubuntu1
I do not know how to see the hardware timing settings. Is that an option on
the bios setup?
Best regards,
Duarte Molha
On Nov 18, 2007 6:04 PM, Theodore Ts'o <[EMAIL PROTECTED]> wrote:
> When re
When reporting problems, please tell us which version of e2fsprogs and
what version of ubuntu you are using. Also whether you have your
hardware clock ticking localtime or UTC. Otherwise a "same here" isn't
very useful
--
fsck on every (re)boot
https://bugs.launchpad.net/bugs/63175
You rec
same problem here. The fsck check slows down the startup time
dramatically.
--
fsck on every (re)boot
https://bugs.launchpad.net/bugs/63175
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
Same problem here... leaving in dublin GMT = London
--
fsck on every (re)boot
https://bugs.launchpad.net/bugs/63175
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://l
Although you say this effects only people east of Greenwich, I am based
in London and still experience this bug. Can provide more info if
needed.
--
fsck on every (re)boot
https://bugs.launchpad.net/bugs/63175
You received this bug notification because you are a member of Ubuntu
Bugs, which is t
** Changed in: e2fsprogs (Ubuntu Gutsy)
Assignee: Ian Jackson (ijackson) => (unassigned)
** Changed in: e2fsprogs (Ubuntu)
Assignee: Ian Jackson (ijackson) => (unassigned)
--
fsck on every (re)boot
https://bugs.launchpad.net/bugs/63175
You received this bug notification because you are
We already have a different ubiquity bug for that (bug 37750).
--
fsck on every (re)boot
https://bugs.launchpad.net/bugs/63175
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.co
2.13-8ubuntu1 uploaded.
I'm leaving this bug open so that it can be used for the ubiquity change
to prompt for "BIOS clock in localtime or UTC?" and thereby set things
up for hwclockfirst.sh to do the right thing.
--
fsck on every (re)boot
https://bugs.launchpad.net/bugs/63175
You received this
I'm fine with -8ubuntu1
--
fsck on every (re)boot
https://bugs.launchpad.net/bugs/63175
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/list
** Changed in: e2fsprogs (Ubuntu Gutsy)
Target: ubuntu-7.10-rc => None
--
fsck on every (re)boot
https://bugs.launchpad.net/bugs/63175
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@
See http://bugs.debian.org/443487 for some detail on the issue. The
affected users are anyone who has their BIOS time set to localtime, and
is east of Greenwich. Solving this for ubiquity installs requires
allowing the user to tell the installed system that this is the case
(new question in ubiqu
A question for the release team:
To fix this bug, we need to upload a util-linux newer than -6ubuntu1,
which raises the question of whether you want me to upload -6ubuntu2, or
-8ubuntu1. Of potential interest to the release in their own right are:
- mount: doesn't drop privileges properly whe
I just wanted to add, that now Ive upgraded my laptop and reinstalled my
desktop with Kubuntu Gutsy Beta. Both machines have one FAT32-partition
(details can be found in my post above) and the desktop is still the
only one to suffer from this problem. Editing /etc/fstab so that the
FAT32-partition
moving milestone to RC
** Changed in: e2fsprogs (Ubuntu Gutsy)
Target: ubuntu-7.10-beta => ubuntu-7.10-rc
--
fsck on every (re)boot
https://bugs.launchpad.net/bugs/63175
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
u
Moving milestone to beta.
** Changed in: e2fsprogs (Ubuntu Gutsy)
Target: tribe-6 => ubuntu-7.10-beta
--
fsck on every (re)boot
https://bugs.launchpad.net/bugs/63175
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubunt
Setting status back to New as logs Michael asked for were supplied.
** Changed in: e2fsprogs (Ubuntu Gutsy)
Status: Incomplete => New
--
fsck on every (re)boot
https://bugs.launchpad.net/bugs/63175
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bu
** Description changed:
** Tags added: iso-testing
--
fsck on every (re)boot
https://bugs.launchpad.net/bugs/63175
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://l
** Changed in: e2fsprogs (Ubuntu Gutsy)
Assignee: Michael Vogt => Ian Jackson
--
fsck on every (re)boot
https://bugs.launchpad.net/bugs/63175
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
Then I'm sorry for my mistake
Like old man say RTFM is the answer.
--
fsck on every (re)boot
https://bugs.launchpad.net/bugs/63175
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubun
In correct, "tune2fs -c 0" does NOT mean skip all time-based checks.
"tune2fs -c 0" means to skip checks based on number of mounts. To
disable all time-based checks, you need to use "tune2fs -i 0". Read
the tune2fs man page, please!! The bug in this case seems to be in your
understanding of tu
Hi
Nice work to figure why this things happend and thank you for the answer.
Is ok when i have set something more than zero value on tune2fs -c but when i
set tune2fs -c 0 that means to skip all the time dont care about what is the
time of system.
This is what I consider bug of e2fsck for any val
>What I notice is that the last checked time doesn't seem to be getting
updated. It shows Jan 1, 1970 - even though if just ran through fsck 30
minutes ago, and every >time I boot.
In humandoing's case, it looks like the problem is that the battery for
his CMOS system clock is dead, so the time is
>I still dont get the proper answer at this simple question on each bug reports.
>Why settings made by tune2fs isnt check by fsck.
E2fsck is checking the superblock settings made by tune2fs. However, in
order to perform the check based on times since last fsck time, e2fsck
requires that the syste
Moving milestone forward.
** Changed in: e2fsprogs (Ubuntu Gutsy)
Target: tribe-5 => tribe-6
--
fsck on every (re)boot
https://bugs.launchpad.net/bugs/63175
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs ma
Thanks for the answer.
I still dont get the proper answer at this simple question on each bug reports.
Why settings made by tune2fs isnt check by fsck.
--
fsck on every (re)boot
https://bugs.launchpad.net/bugs/63175
You received this bug notification because you are a member of Ubuntu
Bugs, which
(Disabling the periodic fsck is Bug #3581 . That bug isn't about very
frequent fscks though)
--
fsck on every (re)boot
https://bugs.launchpad.net/bugs/63175
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing li
Hi
First sorry for my english.
I try to lose that fsck on /dev/md0 at each boot time wher sepnd about 5-10min
long to finish.
I set tune2fs -c 0 /dev/md0
Was ignored still doing fsck
Maybe was a stupid things but i try to boot with fastboot parameter on grub
something like this:
title
** Summary changed:
- Edgy Beta -- fsck on every (re)boot
+ fsck on every (re)boot
--
fsck on every (re)boot
https://bugs.launchpad.net/bugs/63175
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
44 matches
Mail list logo
