← Back to team overview

kernel-packages team mailing list archive

[Bug 1273776] Re: same ext4 corruption in multiple systems

 

Sorry maybe it was not clear, my fault. I can't boot the dom disk with
problems so i've attached it to another system and mounted it in ~/a/m.
I've run the tar command on the whole mounted partition (~/a/m -> / on
faulted disk). If you think you still need tar -cvf i can provide it,
please tell me. I've never tried to tar that directory but it's not a
tar problem. I can't access some files/directories on this partition
because the ext4 filesystem is ruined. I always used this kernel so i
don't know if it was working on previous versions. I'm also not able to
test because i'm not able to replicate the problem. I can only wait for
angry clients :)

-- 
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/1273776

Title:
  same ext4 corruption in multiple systems

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  We are using ext4 as the root filesystem for our server based on
  ubuntu precise 12.04.2 (kernel version 3.8.0-31-generic
  #46~precise1-Ubuntu). The same image for the root filesystem is copied
  over and over to different dom disks so all servers have the same
  partition data. It happened to three of our clients a root file system
  corruption. I'm attaching parted and e2fsck log output. Two systems
  have different motherboard and different cpu so it doesn't seem to be
  hardware dependent. I don't get errors while using dd to copy data
  from the drive but i have errors if i try to use tar:

  root:~/a# tar cf sda.tar m
  tar: m/lib/x86_64-linux-gnu: Cannot stat: Input/output error

  If i look at the partition's content i see that x86_64-linux-gnu is
  now a file and not a directory. I have exactly the same problem on the
  others servers. What can be the problem? What can i do?

  The system is 64bit and the root file system is created with:
  mkfs.ext4 -F -m 1

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


References