[Bug 922765] [NEW] grub os-prober scans iSCSI volumes even if used in virtual machines

Fri Jan 27 18:55:43 UTC 2012

Public bug reported:

In a KVM guest booting from an iSCSI disk I had a filesystem error that
remounted the root of the guest as read-only.

When looking at the KVM host's logs I noticed that periodically, the
guest root partition (sdc1) was being mounted by the os-probe script
when the guest was running.

This seems to be the cause of the file system errors occurring on the
guest.

This is a host log:

Jan 21 06:39:20 host kernel: [8064092.455886] EXT3-fs (sdc1): recovery required on readonly filesystem
Jan 21 06:39:20 host kernel: [8064092.455897] EXT3-fs (sdc1): write access will be enabled during recovery
Jan 21 06:39:20 host kernel: [8064092.456403] EXT3-fs: barriers not enabled
Jan 21 06:39:20 host kernel: [8064092.457129] EXT3-fs (sdc1): orphan cleanup on readonly fs
Jan 21 06:39:20 host kernel: [8064092.457606] EXT3-fs (sdc1): warning: ext3_orphan_get: bad orphan inode 229513!  e2fsck was run?
Jan 21 06:39:20 host kernel: [8064092.457627] EXT3-fs (sdc1): recovery complete
Jan 21 06:39:20 host kernel: [8064092.458658] EXT3-fs (sdc1): mounted filesystem with ordered data mode
Jan 21 06:39:20 host kernel: [8064092.930034] EXT3-fs: barriers not enabled
Jan 21 06:39:20 host kernel: [8064092.930758] EXT3-fs (sdc1): mounted filesystem with ordered data mode
Jan 21 06:40:14 host kernel: [8064146.649484] EXT3-fs (sdc1): recovery required on readonly filesystem
Jan 21 06:40:14 host kernel: [8064146.649494] EXT3-fs (sdc1): write access will be enabled during recovery
Jan 21 06:40:14 host kernel: [8064146.649994] EXT3-fs: barriers not enabled
Jan 21 06:40:14 host kernel: [8064146.650720] EXT3-fs (sdc1): orphan cleanup on readonly fs
Jan 21 06:40:14 host kernel: [8064146.651165] EXT3-fs (sdc1): warning: ext3_orphan_get: bad orphan inode 229513!  e2fsck was run?
Jan 21 06:40:14 host kernel: [8064146.651185] EXT3-fs (sdc1): recovery complete
Jan 21 06:40:14 host kernel: [8064146.652291] EXT3-fs (sdc1): mounted filesystem with ordered data mode
Jan 21 06:40:14 host kernel: [8064147.179934] EXT3-fs: barriers not enabled
Jan 21 06:40:14 host kernel: [8064147.181244] EXT3-fs (sdc1): mounted filesystem with ordered data mode

This is a guest log:

Jan 22 06:25:16 guest kernel: [677006.974161] EXT3-fs error (device vda1): ext3_free_blocks_sb: bit already cleared for block 923781
Jan 22 06:25:16 guest kernel: [677006.975070] Aborting journal on device vda1.
Jan 22 06:25:16 guest kernel: [677007.014916] Remounting filesystem read-only
Jan 22 06:25:16 guest kernel: [677007.016684] EXT3-fs error (device vda1): ext3_free_blocks_sb: bit already cleared for block 923782
Jan 22 06:25:16 guest kernel: [677007.018753] EXT3-fs error (device vda1): ext3_free_blocks_sb: bit already cleared for block 923783
Jan 22 06:25:16 guest kernel: [677007.020878] EXT3-fs error (device vda1): ext3_free_blocks_sb: bit already cleared for block 923784
Jan 22 06:25:16 guest kernel: [677007.022912] EXT3-fs error (device vda1): ext3_free_blocks_sb: bit already cleared for block 923785
Jan 22 06:25:16 guest kernel: [677007.024949] EXT3-fs error (device vda1): ext3_free_blocks_sb: bit already cleared for block 923786
Jan 22 06:25:16 guest kernel: [677007.027096] EXT3-fs error (device vda1): ext3_free_blocks_sb: bit already cleared for block 923787
Jan 22 06:25:16 guest kernel: [677007.029190] EXT3-fs error (device vda1): ext3_free_blocks_sb: bit already cleared for block 923788
Jan 22 06:25:16 guest kernel: [677007.031572] EXT3-fs error (device vda1): ext3_free_blocks_sb: bit already cleared for block 923789
Jan 22 06:25:16 guest kernel: [677007.033685] EXT3-fs error (device vda1): ext3_free_blocks_sb: bit already cleared for block 923790
Jan 22 06:25:16 guest kernel: [677007.035775] EXT3-fs error (device vda1): ext3_free_blocks_sb: bit already cleared for block 923791
Jan 22 06:25:16 guest kernel: [677007.036895] EXT3-fs error (device vda1): ext3_free_blocks_sb: bit already cleared for block 923792
Jan 22 06:25:16 guest kernel: [677007.037754] EXT3-fs error (device vda1) in ext3_reserve_inode_write: Journal has aborted
Jan 22 06:25:16 guest kernel: [677007.038550] EXT3-fs error (device vda1) in ext3_truncate: Journal has aborted
Jan 22 06:25:16 guest kernel: [677007.039346] EXT3-fs error (device vda1) in ext3_reserve_inode_write: Journal has aborted
Jan 22 06:25:16 guest kernel: [677007.040169] EXT3-fs error (device vda1) in ext3_orphan_del: Journal has aborted
Jan 22 06:25:16 guest kernel: [677007.040927] EXT3-fs error (device vda1) in ext3_reserve_inode_write: Journal has aborted

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: grub-pc 1.98-1ubuntu12
ProcVersionSignature: Ubuntu 2.6.38-13.53~lucid1-server 2.6.38.8
Uname: Linux 2.6.38-13-server x86_64
Architecture: amd64
Date: Fri Jan 27 18:16:46 2012
InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64 (20100427)
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: grub2

** Affects: grub2 (Ubuntu)
     Importance: Undecided
         Status: New

** Tags: amd64 apport-bug lucid

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/922765

Title:
  grub os-prober scans iSCSI volumes even if used in virtual machines

Status in “grub2” package in Ubuntu:
  New

Bug description:
  In a KVM guest booting from an iSCSI disk I had a filesystem error
  that remounted the root of the guest as read-only.

  When looking at the KVM host's logs I noticed that periodically, the
  guest root partition (sdc1) was being mounted by the os-probe script
  when the guest was running.

  This seems to be the cause of the file system errors occurring on the
  guest.

  This is a host log:

  Jan 21 06:39:20 host kernel: [8064092.455886] EXT3-fs (sdc1): recovery required on readonly filesystem
  Jan 21 06:39:20 host kernel: [8064092.455897] EXT3-fs (sdc1): write access will be enabled during recovery
  Jan 21 06:39:20 host kernel: [8064092.456403] EXT3-fs: barriers not enabled
  Jan 21 06:39:20 host kernel: [8064092.457129] EXT3-fs (sdc1): orphan cleanup on readonly fs
  Jan 21 06:39:20 host kernel: [8064092.457606] EXT3-fs (sdc1): warning: ext3_orphan_get: bad orphan inode 229513!  e2fsck was run?
  Jan 21 06:39:20 host kernel: [8064092.457627] EXT3-fs (sdc1): recovery complete
  Jan 21 06:39:20 host kernel: [8064092.458658] EXT3-fs (sdc1): mounted filesystem with ordered data mode
  Jan 21 06:39:20 host kernel: [8064092.930034] EXT3-fs: barriers not enabled
  Jan 21 06:39:20 host kernel: [8064092.930758] EXT3-fs (sdc1): mounted filesystem with ordered data mode
  Jan 21 06:40:14 host kernel: [8064146.649484] EXT3-fs (sdc1): recovery required on readonly filesystem
  Jan 21 06:40:14 host kernel: [8064146.649494] EXT3-fs (sdc1): write access will be enabled during recovery
  Jan 21 06:40:14 host kernel: [8064146.649994] EXT3-fs: barriers not enabled
  Jan 21 06:40:14 host kernel: [8064146.650720] EXT3-fs (sdc1): orphan cleanup on readonly fs
  Jan 21 06:40:14 host kernel: [8064146.651165] EXT3-fs (sdc1): warning: ext3_orphan_get: bad orphan inode 229513!  e2fsck was run?
  Jan 21 06:40:14 host kernel: [8064146.651185] EXT3-fs (sdc1): recovery complete
  Jan 21 06:40:14 host kernel: [8064146.652291] EXT3-fs (sdc1): mounted filesystem with ordered data mode
  Jan 21 06:40:14 host kernel: [8064147.179934] EXT3-fs: barriers not enabled
  Jan 21 06:40:14 host kernel: [8064147.181244] EXT3-fs (sdc1): mounted filesystem with ordered data mode

  This is a guest log:

  Jan 22 06:25:16 guest kernel: [677006.974161] EXT3-fs error (device vda1): ext3_free_blocks_sb: bit already cleared for block 923781
  Jan 22 06:25:16 guest kernel: [677006.975070] Aborting journal on device vda1.
  Jan 22 06:25:16 guest kernel: [677007.014916] Remounting filesystem read-only
  Jan 22 06:25:16 guest kernel: [677007.016684] EXT3-fs error (device vda1): ext3_free_blocks_sb: bit already cleared for block 923782
  Jan 22 06:25:16 guest kernel: [677007.018753] EXT3-fs error (device vda1): ext3_free_blocks_sb: bit already cleared for block 923783
  Jan 22 06:25:16 guest kernel: [677007.020878] EXT3-fs error (device vda1): ext3_free_blocks_sb: bit already cleared for block 923784
  Jan 22 06:25:16 guest kernel: [677007.022912] EXT3-fs error (device vda1): ext3_free_blocks_sb: bit already cleared for block 923785
  Jan 22 06:25:16 guest kernel: [677007.024949] EXT3-fs error (device vda1): ext3_free_blocks_sb: bit already cleared for block 923786
  Jan 22 06:25:16 guest kernel: [677007.027096] EXT3-fs error (device vda1): ext3_free_blocks_sb: bit already cleared for block 923787
  Jan 22 06:25:16 guest kernel: [677007.029190] EXT3-fs error (device vda1): ext3_free_blocks_sb: bit already cleared for block 923788
  Jan 22 06:25:16 guest kernel: [677007.031572] EXT3-fs error (device vda1): ext3_free_blocks_sb: bit already cleared for block 923789
  Jan 22 06:25:16 guest kernel: [677007.033685] EXT3-fs error (device vda1): ext3_free_blocks_sb: bit already cleared for block 923790
  Jan 22 06:25:16 guest kernel: [677007.035775] EXT3-fs error (device vda1): ext3_free_blocks_sb: bit already cleared for block 923791
  Jan 22 06:25:16 guest kernel: [677007.036895] EXT3-fs error (device vda1): ext3_free_blocks_sb: bit already cleared for block 923792
  Jan 22 06:25:16 guest kernel: [677007.037754] EXT3-fs error (device vda1) in ext3_reserve_inode_write: Journal has aborted
  Jan 22 06:25:16 guest kernel: [677007.038550] EXT3-fs error (device vda1) in ext3_truncate: Journal has aborted
  Jan 22 06:25:16 guest kernel: [677007.039346] EXT3-fs error (device vda1) in ext3_reserve_inode_write: Journal has aborted
  Jan 22 06:25:16 guest kernel: [677007.040169] EXT3-fs error (device vda1) in ext3_orphan_del: Journal has aborted
  Jan 22 06:25:16 guest kernel: [677007.040927] EXT3-fs error (device vda1) in ext3_reserve_inode_write: Journal has aborted

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: grub-pc 1.98-1ubuntu12
  ProcVersionSignature: Ubuntu 2.6.38-13.53~lucid1-server 2.6.38.8
  Uname: Linux 2.6.38-13-server x86_64
  Architecture: amd64
  Date: Fri Jan 27 18:16:46 2012
  InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64 (20100427)
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: grub2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/922765/+subscriptions