*** This bug is a duplicate of bug 1124803 ***
    https://bugs.launchpad.net/bugs/1124803

Max, as I've understood, "no splash" doesn't disable plymouth. Some people 
suppose that the freezed plymouth is the cause:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1019347
I've decided to find it out and totally purged plymouth from system. But that 
didn't help.

So, what do we have now?
I've modified /etc/init.d/umountroot script (part at 86 line):
=========================
        for i in 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
        do

                mount    $MOUNT_FORCE_OPT -n -o remount,ro -t dummytype 
dummydev / 2>/dev/null \
                || mount $MOUNT_FORCE_OPT -n -o remount,ro              
dummydev / 2>/dev/null \
                || mount $MOUNT_FORCE_OPT -n -o remount,ro                      
 /
                ES=$?
#       [ "$VERBOSE" = no ] || log_action_end_msg $ES
                log_action_end_msg $ES
                if [ $ES -gt 0 ]
                then
                    LOG=/mega-log-`date +%s`
                    echo "`date`: Attempt ${i}: remount rootfs failed! Trying 
again..." #| tee -a $LOG
                    echo "`date`: Attempt ${i}: remount rootfs failed! Trying 
again..." >> $LOG
#                    sleep 1
                    { cat /proc/mounts ;  echo ; ps aux ; echo ; /usr/bin/lsof 
; echo ; } >> $LOG
                    /bin/fuser -v -m -u / 1>/dev/null 2>> $LOG
                    sleep 1
                else
                    break
                fi
        done
=========================

Today's morning I've got a 21 message "/ is busy" at shutdown.
Early, I thought that the cause is that some processes are accessing the disk 
during shutdown (writing). Some processes which are not terminated on time, so 
" / is busy " message appears.
Now I'm looking into logs and...  Well, looks like it isn't the real cause.
I don't see any files opened for writing (except pipe, @/com/ubuntu/upstart, 
/dev/null and /dev/console).
So, more and more I think, that this bug is in 'init/upstart'... or in kernel!
It's not so easy to reproduce it. I've tried a lot of times to reboot machine 
under heavy cpu and I/O load and bug doesn't apper (a lot of times in about 
10-15 minutes).
But bug appears more frequently when uptime is high enough (at least 1/2 of a 
day).
Steps to reproduce: push power button from running X session.

One more interesting thing: my root partition is on usb hard drive.

If I'll have some more free time near future, I'll try to test it with a
new kernel ( > 3.5).


** Attachment added: "mega-log-1365656098"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1073433/+attachment/3640749/+files/mega-log-1365656098

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager 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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to