Public bug reported:
I upgraded /backup on my lucid amd64 desktop machine to ext4 yesterday
according to
http://ext4.wiki.kernel.org/index.php/Ext4_Howto#Converting_an_ext3_filesystem_to_ext4
It passed the fsck and was working ok, but while making a backup today I
got an IO error and this message in dmesg:
Feb 25 17:45:37 grace kernel: [37152.894557] EXT4-fs error (device
dm-4): make_indexed_dir: invalid rec_len for '..' in inode 2933963
I unmounted it and ran fsck, which shows many messages like
grace% sudo nice fsck -Cfv /dev/vg_main/backup
fsck from util-linux-ng 2.17
e2fsck 1.41.10 (10-Feb-2009)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
First entry '%45ncoding%41dapter.py-20060113032051-4d7e1d8c1e38b4a1.kndx'
(inode=1458904) in directory inode 131130
(/grace/mbp/bzr/20070706/.bzr/repository/knits/31) should be '.'
Fix<y>? yes
Setting filetype for entry '.' in
/grace/mbp/bzr/20070706/.bzr/repository/knits/31 (131130) to 2.
Missing '..' in directory inode 131130.
Fix<y>? yes
Setting filetype for entry '..' in
/grace/mbp/bzr/20070706/.bzr/repository/knits/31 (131130) to 2.
Entry '..' in /grace/mbp/bzr/20070706/.bzr/repository/knits/31 (131130) is
duplicate '..' entry.
Fix<y>? yes
Entry '.' in /grace/mbp/bzr/20070706/.bzr/repository/knits/31 (131130)
is a link to '.' Clear<y>? yes
First entry '%52%45%41%44%4d%45-20050309040720-8f368abf9f346b9d.kndx'
(inode=132214) in directory inode 131139
(/grace/mbp/bzr/20070706/.bzr/repository/knits/3a) should be '.'
Fix<y>? yes
Setting filetype for entry '.' in
/grace/mbp/bzr/20070706/.bzr/repository/knits/3a (131139) to 2.
Missing '..' in directory inode 131139.
Fix<y>? yes
... and on and on.
ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
**** List of PLAYBACK Hardware Devices ****
card 1: U0x41e0x30d3 [USB Device 0x41e:0x30d3], device 0: USB Audio [USB Audio]
Subdevices: 0/1
Subdevice #0: subdevice #0
Architecture: amd64
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 1: U0x41e0x30d3 [USB Device 0x41e:0x30d3], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: mbp 3010 F.... pulseaudio
/dev/snd/pcmC1D0p: mbp 3010 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card1.Amixer.info:
Card hw:1 'U0x41e0x30d3'/'USB Device 0x41e:0x30d3 at usb-0000:00:1d.7-5.1.4,
full speed'
Mixer name : 'USB Mixer'
Components : 'USB041e:30d3'
Controls : 7
Simple ctrls : 3
Date: Thu Feb 25 20:34:52 2010
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
Frequency: Once a day.
HibernationDevice: RESUME=/dev/mapper/vg_main-swap
IwConfig:
lo no wireless extensions.
eth0 no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. 965P-DS3
NonfreeKernelModules: nvidia
Package: linux-image-2.6.32-14-generic 2.6.32-14.20
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-14-generic
root=/dev/mapper/vg_main-lucid_64 ro clock=hpet quiet splash
ProcEnviron:
PATH=(custom, user)
LANG=en_AU.utf8
SHELL=/bin/zsh
ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
Regression: Yes
RelatedPackageVersions: linux-firmware 1.30
Reproducible: No
RfKill:
SourcePackage: linux
TestedUpstream: No
Uname: Linux 2.6.32-14-generic x86_64
WpaSupplicantLog:
dmi.bios.date: 01/12/2007
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F10
dmi.board.name: 965P-DS3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias:
dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd01/12/2007:svnGigabyteTechnologyCo.,Ltd.:pn965P-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rn965P-DS3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: 965P-DS3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug lucid needs-upstream-testing regression-potential
--
lucid ext4 make_indexed_dir: invalid rec_len for '..' in inode
https://bugs.launchpad.net/bugs/527644
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
