xfs
[Top] [All Lists]

xfs bug

To: linux-xfs@xxxxxxxxxxx
Subject: xfs bug
From: Yonathan Dossow <ydossow@xxxxxx>
Date: Tue, 25 Apr 2006 22:17:43 -0400
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.4.2.1i
hi.

i do a xfs_repair /dev/hda6, and i get the following:


-- begin error --

Phase 1 - find and verify superblock...
Phase 2 - using internal log
        - zero log...
        - scan filesystem freespace and inode maps...
        - found root inode chunk
Phase 3 - for each AG...
        - scan and clear agi unlinked lists...
        - process known inodes and perform inode discovery...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - agno = 4
        - agno = 5
correcting nblocks for inode 48838848, was 0 - counted 1
        - agno = 6
        - agno = 7
        - agno = 8
        - agno = 9
        - agno = 10
        - agno = 11
        - agno = 12
        - agno = 13
        - agno = 14
        - agno = 15
        - process newly discovered inodes...
Phase 4 - check for duplicate blocks...
        - setting up duplicate extent list...
        - clear lost+found (if it exists) ...
        - clearing existing "lost+found" inode
        - deleting existing "lost+found" entry
        - check for inodes claiming duplicate blocks...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - agno = 4
        - agno = 5
data fork in regular inode 48838848 claims used block 3052432
correcting nblocks for inode 48838848, was 1 - counted 0
        - agno = 6
        - agno = 7
        - agno = 8
        - agno = 9
        - agno = 10
        - agno = 11
        - agno = 12
        - agno = 13
        - agno = 14
        - agno = 15
Phase 5 - rebuild AG headers and trees...
        - reset superblock...
Phase 6 - check inode connectivity...
        - resetting contents of realtime bitmap and summary inodes
        - ensuring existence of lost+found directory
        - traversing filesystem starting at / ... 
corrupt dinode 48838848, extent total = 1, nblocks = 0.  This is a bug.
Please report it to linux-xfs@xxxxxxxxxxxx

fatal error -- couldn't map inode 48838848, err = 990

-- end error --

mi partition table:

[root@alcatraz ~]# fdisk -l /dev/hda

Disk /dev/hda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hda1               1        2867    23029146   83  Linux
/dev/hda2            2868        4779    15358140   83  Linux
/dev/hda3            4780       14593    78830955    f  W95 Ext'd (LBA)
/dev/hda5            4780        4841      497983+  82  Linux swap /
Solaris
/dev/hda6            4842        8275    27583573+  83  Linux
/dev/hda7            8276       10825    20482843+  83  Linux
/dev/hda8           10826       14593    30266428+  83  Linux


what can i do?. thanks.
-- 
Yonathan H. Dossow Acuña                       http://kronin.bla.cl
Estudiante Ingenieria Civil Informatica
Universidad Tecnica Federico Santa Maria          Valparaiso, Chile


<Prev in Thread] Current Thread [Next in Thread>
  • xfs bug, Yonathan Dossow <=