** Changed in: linux (Ubuntu)
Status: Invalid => Incomplete
** Changed in: upstart
Status: Invalid => Confirmed
** Changed in: upstart (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
** Changed in: upstart
Status: Confirmed => Invalid
** Changed in: upstart (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
** Changed in: network-manager (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1073433
Title:
Ext4 corruption associated with shutdown of U
Looks like bug #1169614 was finally fixed.
But there's one more bug which cause same problem: bug #1307008
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1073433
Title:
Ext4 corruption
** Tags added: trusty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1073433
Title:
Ext4 corruption associated with shutdown of Ubuntu 12.10
Status in Upstart:
Confirmed
Status in “li
14.04 — it's still a problem (dhclient issue).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1073433
Title:
Ext4 corruption associated with shutdown of Ubuntu 12.10
Status in Upstart:
On Wed, Jan 22, 2014 at 04:13:19PM -, Max wrote:
> Steve Dodd:
> > Last time I did, my own problems were caused by dhclient and ureadahead..
>
> It is not an ureadahead issue, it is an extra fork in upstart to launch
> shell for ureadahead if more than one partition mounted.
Yes, I know - I
On 01/22/2014 05:51 PM, Steve Langasek wrote:
> On Wed, Jan 22, 2014 at 09:19:13AM -, Benny wrote:
>> Lennert of systemd refers to this bug on google+. He outlines a fix for
>> the simple case:
>
> The fix he outlines is not for this bug. It's not for a bug we have in
> upstart in Ubuntu at al
On Wed, Jan 22, 2014 at 05:11:03PM -, Clint Byrum wrote:
> The other one is the one that would sweep up the mess we occasionally
> see when something misbehaves.
> I'd like to see Ubuntu's shutdown do more to protect against that
> failure mode.
I would, too, but I don't agree that the method
Excerpts from Steve Langasek's message of 2014-01-22 16:51:06 UTC:
> On Wed, Jan 22, 2014 at 09:19:13AM -, Benny wrote:
> > Lennert of systemd refers to this bug on google+. He outlines a fix for
> > the simple case:
>
> The fix he outlines is not for this bug. It's not for a bug we have in
>
On Wed, Jan 22, 2014 at 09:19:13AM -, Benny wrote:
> Lennert of systemd refers to this bug on google+. He outlines a fix for
> the simple case:
The fix he outlines is not for this bug. It's not for a bug we have in
upstart in Ubuntu at all; we already reliably ensure telinit u on upgrade of
a
Steve Dodd:
> Last time I did, my own problems were caused by dhclient and ureadahead..
It is not an ureadahead issue, it is an extra fork in upstart to launch
shell for ureadahead if more than one partition mounted.
--
You received this bug notification because you are a member of Kernel
Packag
This does seem to be getting kind of embarassing. With modern journalled
filesystems on relatively straightforward hardware configs an unclean
shutdown shouldn't be the end of the world (after all, power failures
can happen), but it's not "nice" either.
Unfortunately we also seem to have a hell o
Lennert of systemd refers to this bug on google+. He outlines a fix for
the simple case:
https://plus.google.com/115547683951727699051/posts/LjkLwkeDiLc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpa
I'd guess patch in bug 1169614 would help in my case (dhclient process).
Any progress on evaluating and possibly including the patch provided in
that bug ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launc
In my case it's a dhclient process that likely respawns and prevents
remount to read-only of root fs, due to a lease file opened for writing
under /var/lib/NetworkManager/.. Result is unclean shutdown and recovery
of dirty root file system on next boot.
Attaching lsof output obtained just before c
You are definivly right in that case
a bug is allready opened(Bug #1073433 ) as i writing a comment to it
The normal user wants a clean shutdown or reboot and as I wrote its a dirty
hack until this problem is resolved by the maintainers
we know the schutdown process isn't working correctly as i
Excerpts from Bernd's message of 2014-01-05 21:37:21 UTC:
> due the respawn of some processes i think they are (re)started again even on
> shutdown
> so they are running if the / is remounted readonly
> and that is why it fails
>
> i think upstart should insure that all processes are killed (
due the respawn of some processes i think they are (re)started again even on
shutdown
so they are running if the / is remounted readonly
and that is why it fails
i think upstart should insure that all processes are killed (also the
respawning) at the moment we mount / readonly on halt or rebo
I have tried some workarounds from the comments and nothing seems to
work. Fsck still runs at every boot. Bootchart included.
** Attachment added: "Bootchart image"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1073433/+attachment/3929572/+files/andrej-namizni-saucy-20131215-1.png
--
Regardless of that one comment above. But it is really frustrating if
now the user's of ubuntu get blamed for not filing the correct bug. Dear
folks at Canonical, you have so much information in this one thread,
about how to reproduce this error. I'm not that experienced. So please,
could someone r
Excerpts from Alexander's message of 2013-10-25 05:39:16 UTC:
> Guys, come on!
> What the heck network-manager and network connections are you talking about?!
> This really pissed me off already!
> As I've said earlier, the problem is NOT in network-manager!
> https://bugs.launchpad.net/ubuntu/+sou
So when I wrote 6 months ago that:
> If you can reproduce this issue, please file a new bug report against
> the sysvinit-utils package with details. It is certainly unrelated to the
> common issue being described here.
Rather than doing this to help yourself, you switch distros, decide that
upst
Guys, come on!
What the heck network-manager and network connections are you talking about?!
This really pissed me off already!
As I've said earlier, the problem is NOT in network-manager!
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1073433/comments/105
because it appears even when network
Excerpts from Steve Dodd's message of 2013-10-21 16:16:29 UTC:
> That sounds plausible - I would guess wireless connections are usually torn
> down at the end of the user session (i.e. logout) whereas I assume wired
> connections persist right to system shutdown??
In theory they're brought down wh
On Wed, Oct 23, 2013 at 10:15:46PM -, Gregor Larson wrote:
> init 1 root 15w REG 8,24 1134 438383
> /var/log/upstart/mountall.log
mountall is a service that's supposed to run once at boot and then exit. If
mountall is still running when you shut the system down, then
I did a bit of hacking on init.d/umountroot, adding lsof and ps -ef after the
remount fails.
I could see that dhclient was still running, so I added before the remount:
pkill -9 dhclient
After this change, dhclient was gone, but the remount still failed. In
lsof output I can see:
init
Sorry, forgot to added version info to #146
Ubuntu Saucy 32-bit, package version: upstart 1.10-0ubuntu7 i386
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1073433
Title:
Ext4 corruptio
That sounds plausible - I would guess wireless connections are usually torn
down at the end of the user session (i.e. logout) whereas I assume wired
connections persist right to system shutdown??
On Oct 21, 2013 3:01 PM, "Christian Niemeyer"
wrote:
> It occurs that the problem did *not* exist aft
It occurs that the problem did *not* exist after a recent clean install
of 13.10 (64bit Desktop CD) on a friend's notebook. While it still
happens on my desktop PC.
Differences:
On the notebook we used wireless (b43 out of the box) internet during
installation. Reboot into new system, login, shut
I'm seeing this in 13.10 as well.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1073433
Title:
Ext4 corruption associated with shutdown of Ubuntu 12.10
Status in Upstart:
Confirmed
S
Yeah, still exists in 13.10.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1073433
Title:
Ext4 corruption associated with shutdown of Ubuntu 12.10
Status in Upstart:
Confirmed
Status
This still happens in 13.10 (saucy). This time I installed the Beta-2 of
Lubuntu (thus using an lxsession). Reboot or shutdown fails everytime.
It hangs for around ten seconds, then it reboots and fsck shows "deleted
orphaned inode".
Only helps to uninstall network-manager-*, nm-*, modemmanager,
u
Dmitry, I confirm your solution. I already uninstalled ureadahead (no
need for it with a SSD).
I added killall dhclient to my /etc/init.d/umountfs (at the beginning of
the do_stop function).
This problem happens for me only when I use the regular wired ethernet
on my ThinkPad X230 (not just when
I've tried patches in mentioned in comment #137, but they didn't help.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1073433
Title:
Ext4 corruption associated with shutdown of Ubuntu 12
I have the same problem on 13.04, which is solved by 2 steps (as mentioned
above):
1) uninstalling ureadahead or adding "console none" to
/etc/init/ureadahead-other.conf
2) killing dhclient in umountfs.
Indeed, why it has not been fixed for "years"
--
You received this bug notification bec
36 matches
Mail list logo
