kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #24459
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
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 reproduce this error (take a machine without any wireless
capabilities) and then file the correct bug, if this bug report here is
not "good enough" for you.
It's pretty amazing that a bug that causes **filesystem errors** (if
minor or not minor) does not get fixed at all and now the users get
partly blamed for not filing the bug on the correct package? Hello? A
default installation causes filesystem errors, reproduceable. Would
someone please take those hints in this thread seriously? Like: install
on a machine with a wired connection on no wireless adapters. I can
reproduce this 100%.
My fix is (taken from this thread): "console none" in /etc/init
/ureadahead-other.conf OR uninstalling ureadahead at all.
And more important in /etc/init/umountfs adding the following lines in
the beginning of the file:
service networking stop
sleep 1
service networking start
sleep 1
service networking stop
sleep 1
killall dhclient
sleep 1
That worked for me. I don't know what package to file this bug against, because it seems that it happens out of certain hardware and interaction between different packages. I'm not blaming upstart at all. I just want this CRITICAL bug to be fixed. It is around since 12.04/12.10. That's "amazing".
--
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 “linux” package in Ubuntu:
Incomplete
Status in “network-manager” package in Ubuntu:
Triaged
Status in “upstart” package in Ubuntu:
Confirmed
Bug description:
1. Format and label a target Ext4 partion using Ubuntu 12.04
2. Install 64bit 12.10 OS using that target without reformatting it
3. Shut down
4. Boot an alternate copy of Ubuntu
5. Restart selecting the newly installed OS
6. Login then shutdown
6. Boot an alternate copy of Ubuntu
7.Fsck the newly installed OS allowing corrections to be made
Each time the the newly installed OS is executed and then shutdown,
even if execution only consists of logging on, a subsequent fsck will
FAIL.
I used Acronis True Image Home 2013 to create an image of the newly
installed 64-bit Ubuntu 12.10, so I can recreate the symptoms of Ext4
filesystem corruption 100% of the time by restoring from the image,
booting, logging on and shutting down.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: linux-image-3.5.0-17-generic 3.5.0-17.28
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
Uname: Linux 3.5.0-17-generic x86_64
ApportVersion: 2.6.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: aguru 1871 F.... pulseaudio
/dev/snd/controlC0: aguru 1871 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Date: Tue Oct 30 22:24:54 2012
HibernationDevice: RESUME=UUID=f22e3fa5-c5c5-41f1-ae5a-49390547cb67
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
IwConfig:
eth0 no wireless extensions.
lo no wireless extensions.
MachineType: System manufacturer P5Q-E
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=ef2c78d5-783a-422a-88f7-27ec09dda0d1 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.5.0-17-generic N/A
linux-backports-modules-3.5.0-17-generic N/A
linux-firmware 1.95
RfKill:
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/06/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2101
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5Q-E
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2101:bd04/06/2009:svnSystemmanufacturer:pnP5Q-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5Q-E
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions