Hello,
I have booted with 2.6.39 from backports and was able to repair the
filesystem. (I took a snapshot of the lun first and tried the repair
on the snapshot first.)
I have attached the output of the repair.
I'm going to reply to the questions I can answer :)
- what steps you
root@cyrprd3:~# xfs_repair -v /dev/mapper/mail22-ds3400-2
Phase 1 - find and verify superblock...
- block cache size set to 4628616 entries
Phase 2 - using internal log
- zero log...
zero_log: head block 476774 tail block 476774
- scan filesystem freespace and inode
Package: linux-2.6
Severity: normal
Hi
I'm seeing the same issue.
Jan 12 21:14:42 cyrprd4 kernel: [2084252.748654] 880aa6ac4000: 49 4e 00 00
02 02 00 00 00 00 03 d4 00 00 00 08 IN..
Jan 12 21:14:42 cyrprd4 kernel: [2084252.748717] Filesystem dm-29: XFS
internal error
Hi
I'm seeing the same issue on r410. 2.6.32-28 with numa=noacpi doesn't
help though. Or isn't this yet in that kernel?
Thanks
Rudy
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
Package: initramfs-tools
Version: 0.98.4
Severity: normal
Hi,
This is a similar problem that was reported in #505440.
The DEVICE variable is leaked into the environment. The mdadm mkconf script
uses DEVICE when it is installing its config file.
In my case DEVICE is set by initramfs-tools to
5 matches
Mail list logo