Ubuntu-lts-3.8.0 kernels corrupt ext[234] filesystems with 1k block size in Xen guests
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Raring |
Fix Released
|
High
|
Unassigned |
Bug Description
We observed a problem with a Postfix database file created by postmap becoming corrupted in a Xen guest when the file was on an ext4 filesystem with a 1kb block size. This was reported to the linux-ext4 list in http://
---
AlsaDevices:
total 0
crw-rw---T 1 root audio 116, 1 Oct 4 19:28 seq
crw-rw---T 1 root audio 116, 33 Oct 4 19:28 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 13.04
HibernationDevice: RESUME=
IwConfig: Error: [Errno 2] No such file or directory
Lspci:
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99
MarkForUpload: True
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
LANGUAGE=en_GB:en
TERM=screen
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
ProcFB: 0 xen
ProcKernelCmdLine: root=/dev/
ProcVersionSign
RelatedPackageV
linux-
linux-
linux-firmware 1.106
RfKill: Error: [Errno 2] No such file or directory
Tags: raring
Uname: Linux 3.8.0-31-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
summary: |
- Ubuntu-lts-3.8.0 corrupt ext[234] filesystems with 1k block zie in Xen - guests + Ubuntu-lts-3.8.0 kernels corrupt ext[234] filesystems with 1k block size + in Xen guests |
affects: | bughelper → linux (Ubuntu) |
Changed in linux (Ubuntu): | |
importance: | Undecided → High |
tags: | added: raring |
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1234662
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.