xfs-masters
[Top] [All Lists]

[xfs-masters] [Bug 11747] New: Cannot chown files + possible FS corrupti

To: xfs-masters@xxxxxxxxxxx
Subject: [xfs-masters] [Bug 11747] New: Cannot chown files + possible FS corruption
From: bugme-daemon@xxxxxxxxxxxxxxxxxxx
Date: Sun, 12 Oct 2008 08:27:25 -0700 (PDT)
Reply-to: xfs-masters@xxxxxxxxxxx
Sender: xfs-masters-bounce@xxxxxxxxxxx
http://bugzilla.kernel.org/show_bug.cgi?id=11747

           Summary: Cannot chown files + possible FS corruption
           Product: File System
           Version: 2.5
     KernelVersion: 2.6.27
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: blocking
          Priority: P1
         Component: XFS
        AssignedTo: xfs-masters@xxxxxxxxxxx
        ReportedBy: v13+kbug@xxxxxxxxxxxx


Latest working kernel version: 2.6.26
Earliest failing kernel version: 2.6.27
Distribution: Debian - Kernel is compiled by myself
Hardware Environment: x86_64, 5GB RAM, S/W RAID-5
Software Environment: Debian testing
Problem Description:

After compiling 2.6.27 and booting to it there were a lot of errors with file
operations at the root filesystem. All of them were complains about Read-only
filesystem. It turned out that with 2.6.27 I can create and remove files,
change their contents but I can't change the file permissions or file times.

chown, tar and other commands gave this kind of errors. strace showed EROFS
return codes from various system calls.

This is happening only at the / filesystem (XFS). Other XFS filesystems worked
OK. Tried remounting it ro and then rw but no change.

Also, after booting to 2.6.27 and back to 2.6.26 and running
xfs_check/xfs_repair, 308 files were placed in /lost+found. xfs_repair was run
under 2.6.26. Them I booted back to 2.6.27 and return xfs_check on / and it
showed more errors. I've not rerun xfs_repair on / since.

Configuration is XFS over software raid5 with 4 disks. Mount options from
/proc/mounts:
/dev/md/6 / xfs rw,noatime,attr2,nobarrier,sunit=128,swidth=256,noquota 0 0
/dev/md/5 /home xfs rw,noatime,attr2,nobarrier,sunit=128,swidth=256,noquota 0 0

/dev/md/6 gives the RO errors, while /dev/md/5 works very well.

While in 2.6.27 I tried mounting /dev/md/6 (/) to another place (/mnt/1) too
and it had the same behavior over there.

2.6.26 still works very well.

Dmesg gave no errors or noticed of XFS for auto-remounting / read-only.

Is there anything more I can try?

Kernel is custom made - not the official Debian.

Steps to reproduce:

Boot to 2.6.27. Most probably happens only to me (?).

From 2.6.26:
# xfs_info /
meta-data=/dev/md/6              isize=256    agcount=24, agsize=610480 blks
         =                       sectsz=4096  attr=2
data     =                       bsize=4096   blocks=14651184, imaxpct=25
         =                       sunit=16     swidth=32 blks
naming   =version 2              bsize=4096  
log      =internal               bsize=4096   blocks=4769, version=2
         =                       sectsz=4096  sunit=1 blks, lazy-count=1
realtime =none                   extsz=131072 blocks=0, rtextents=0

# xfs_info /home
meta-data=/dev/md/5              isize=512    agcount=24, agsize=1220688 blks
         =                       sectsz=4096  attr=2
data     =                       bsize=4096   blocks=29296464, imaxpct=25
         =                       sunit=16     swidth=32 blks
naming   =version 2              bsize=4096  
log      =internal               bsize=4096   blocks=9536, version=2
         =                       sectsz=4096  sunit=1 blks, lazy-count=1
realtime =none                   extsz=131072 blocks=0, rtextents=0


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


<Prev in Thread] Current Thread [Next in Thread>