[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#486582: marked as done (linux-image-2.6.25-1-amd64: fails to mount xfs filesystem: I/O error in filesystem)

Your message dated Sun, 8 Feb 2009 11:33:29 +0100
with message-id <20090208103328.GA4744@galadriel.inutil.org>
and subject line Re: linux-image-2.6.25-1-amd64: fails to mount xfs filesystem: I/O error in filesystem
has caused the Debian Bug report #486582,
regarding linux-image-2.6.25-1-amd64: fails to mount xfs filesystem: I/O error in filesystem
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
486582: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=486582
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.25-1-amd64
Version: 2.6.25-1
Severity: important


This kernel fails to mount xfs filesystems (2.6.24-1-amd64 can mount them
fine).

2.6.24:

   XFS mounting filesystem loop18
   Ending clean XFS mount for filesystem: loop18

2.6.25:

   [   78.284155] XFS: correcting sb_features alignment problem
   [   78.301029] XFS mounting filesystem loop18
   [   78.305029] attempt to access beyond end of device
   [   78.305029] loop19: rw=0, want=131079, limit=131072
   [   78.305029] I/O error in filesystem ("loop18") meta-data dev loop19 block 0x1ffff       ("xlog_bread") error 5 buf count 512
   [   78.305029] XFS: empty log check failed
   [   78.305029] XFS: log mount/recovery failed: error 5
   [   78.305029] XFS: log mount failed

The filesystem is on loop18 and has an external log device of 64mb size
on loop19 (both on loop-aes over lvm, although that is unlikely to be the
problem).

The I/O error is not a physical failure but simply an access beyond the
end of device (xfs asks for sector 131079, but that's beyond the size of
the log device).

2.6.24 mounts the device before and after trying on 2.6.25, so 2.6.25
doesn't corrupt the filesystem, it simply cannot mount it.

As a sidenote, xfs_check _now_ says something about a mismatch between
sb_features and sb_features_bad or something like that (sorry, didn't
write it down), but that might be unrelated (the "correcting sb_features
alignment problem" didn't affect mountability under 2.6.24, I probably
need newer xfsprogs).

-- Package-specific info:

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.24-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-image-2.6.25-1-amd64 depends on:
ii  debconf [debconf-2.0]        1.5.11etch1 Debian configuration management sy
ii  initramfs-tools [linux-initr 0.92b       tools for generating an initramfs
ii  module-init-tools            3.3-pre4-2  tools for managing Linux kernel mo

linux-image-2.6.25-1-amd64 recommends no packages.

-- debconf information excluded

--- End Message ---
--- Begin Message --- 
On Tue, Jun 17, 2008 at 01:12:09AM +0200, Marc Lehmann wrote:
> Package: linux-image-2.6.25-1-amd64
> Version: 2.6.25-1
> Severity: important
> 
> 
> This kernel fails to mount xfs filesystems (2.6.24-1-amd64 can mount them
> fine).

This bug report has been pinged at least twice for more
information, so I'm closing it now.

If anyone reencounters the problem, please reopen this
bug.

Cheers,
        Moritz

--- End Message ---
Reply to: