xfs
[Top] [All Lists]

Re: UPDATE: VERY URGENT: "cp -a" creates mysteriously "hidden" files?!

To: "Seth Mos" <knuffie@xxxxxxxxx>
Subject: Re: UPDATE: VERY URGENT: "cp -a" creates mysteriously "hidden" files?!
From: "Ralf G. R. Bergs" <rabe@xxxxxxxxxxxxxx>
Date: Sun, 30 Dec 2001 09:58:55 +0100
Cc: "Eric Sandeen" <sandeen@xxxxxxx>, "Linux XFS Mailing List" <linux-xfs@xxxxxxxxxxx>
In-reply-to: <Pine.BSI.4.10.10112292316190.28973-100000@xxxxxxxxxxxxx>
Reply-to: "Ralf G. R. Bergs" <rabe@xxxxxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
On Sat, 29 Dec 2001 23:23:03 +0100 (CET), Seth Mos wrote:

>On Sat, 29 Dec 2001, Ralf G. R. Bergs wrote:
>
>> On Sat, 29 Dec 2001 16:08:24 +0100 (CET), Seth Mos wrote:
>> 
>> >It's possible you might had checked out a CVS tree just in between two
>> >fixes where it was broken.
>> 
>> Ok, I've now built a new kernel based upon today's CVS source.
>> 
>> Guess what? The problem's still there, but it seems that things have become 
>> somewhat better. I only received THREE error messages like the following:
>
>At least some progress. I guess you still have some errors in your log. We
>will need to find out what is going on here.
>
>Have you tried running a xfs_repair on it? The last time you lost your
>root inode. Let's see what got hit this time. Have you also tried updating
>your userspace utils?

Ok, before trying this I updated to yesterday's xfsutils.

This is what I got (dramatically truncated because of 60,000 lines output!!!):

Fileserver:/# xfs_repair /dev/sdc5
Phase 1 - find and verify superblock...
Phase 2 - using internal log
        - zero log...
        - scan filesystem freespace and inode maps...
inode chunk claims used block, inobt block - agno 75, bno 3, inopb 16
inode chunk claims used block, inobt block - agno 75, bno 3, inopb 16
inode chunk claims used block, inobt block - agno 75, bno 3, inopb 16
inode chunk claims used block, inobt block - agno 75, bno 3, inopb 16
inode chunk claims used block, inobt block - agno 82, bno 3, inopb 16
inode chunk claims used block, inobt block - agno 82, bno 3, inopb 16
inode chunk claims used block, inobt block - agno 82, bno 3, inopb 16
inode chunk claims used block, inobt block - agno 82, bno 3, inopb 16
[...]
        - found root inode chunk
Phase 3 - for each AG...
        - scan and clear agi unlinked lists...
found inodes not in the inode allocation tree
found inodes not in the inode allocation tree
found inodes not in the inode allocation tree
found inodes not in the inode allocation tree
        - process known inodes and perform inode discovery...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - agno = 4
        - agno = 5
        - agno = 6
        - agno = 7
        - agno = 8
data fork in ino 134217859 claims free block 8388692
data fork in ino 134217859 claims free block 8388693
data fork in ino 134217859 claims free block 8388694
[...]
data fork in ino 134217881 claims free block 8389202
data fork in ino 134217881 claims free block 8389203
        - agno = 9
        - agno = 10
        - agno = 11
        - agno = 12
        - agno = 13
        - agno = 14
        - agno = 15
        - agno = 16
        - agno = 17
        - agno = 18
        - agno = 19
        - agno = 20
        - agno = 21
        - agno = 22
        - agno = 23
        - agno = 24
        - agno = 25
        - agno = 26
        - agno = 27
        - agno = 28
        - agno = 29
        - agno = 30
        - agno = 31
        - agno = 32
        - agno = 33
        - agno = 34
        - agno = 35
        - agno = 36
        - agno = 37
        - agno = 38
        - agno = 39
        - agno = 40
        - agno = 41
        - agno = 42
        - agno = 43
        - agno = 44
        - agno = 45
        - agno = 46
        - agno = 47
        - agno = 48
bad inode format in inode 805306498
bad inode format in inode 805306498
cleared inode 805306498
        - agno = 49
        - agno = 50
        - agno = 51
        - agno = 52
        - agno = 53
        - agno = 54
        - agno = 55
        - agno = 56
        - agno = 57
        - agno = 58
        - agno = 59
        - agno = 60
        - agno = 61
        - agno = 62
        - agno = 63
        - agno = 64
        - agno = 65
        - agno = 66
        - agno = 67
        - agno = 68
        - agno = 69
        - agno = 70
        - agno = 71
        - agno = 72
        - agno = 73
        - agno = 74
data fork in ino 1245087026 claims free block 78882673
data fork in ino 1245087027 claims free block 78882674
data fork in ino 1245087028 claims free block 78882675
data fork in ino 1245087029 claims free block 78882676
data fork in ino 1245087030 claims free block 78882677
data fork in ino 1245087031 claims free block 78882678
data fork in ino 1245087032 claims free block 78882679
data fork in ino 1245105083 claims free block 78883446
data fork in ino 1245119324 claims free block 78884725
data fork in ino 1245119332 claims free block 78884726
data fork in ino 1245119334 claims free block 78884727
data fork in ino 1245119337 claims free block 78884728
data fork in ino 1245119339 claims free block 78884729
data fork in ino 1245119345 claims free block 78886006
data fork in ino 1245261262 claims free block 78894908
data fork in ino 1245261302 claims free block 78894989
data fork in ino 1245312693 claims free block 78895487
        - agno = 75
correcting nblocks for inode 1262068294, was 18446744073709533187 - counted 3
data fork in ino 1262068295 claims free block 78879299
data fork in ino 1262068295 claims free block 78879300
[hundreds of similar lines...]
data fork in ino 1262122881 claims free block 78882725
data fork in ino 1262122881 claims free block 78882726
imap claims in-use inode 1262122881 is free, correcting imap
data fork in ino 1262122882 claims free block 78882727
imap claims in-use inode 1262122882 is free, correcting imap
data fork in ino 1262122883 claims free block 78882728
imap claims in-use inode 1262122883 is free, correcting imap
data fork in ino 1262122884 claims free block 78882729
imap claims in-use inode 1262122884 is free, correcting imap
data fork in ino 1262122885 claims free block 78882730
data fork in ino 1262122885 claims free block 78882731
[...]
data fork in ino 1262122885 claims free block 78882750
data fork in ino 1262122885 claims free block 78882751
imap claims in-use inode 1262122885 is free, correcting imap
data fork in ino 1262122886 claims free block 78882752
imap claims in-use inode 1262122886 is free, correcting imap
data fork in ino 1262122887 claims free block 78882753
data fork in ino 1262122887 claims free block 78882754
data fork in ino 1262122887 claims free block 78882755
data fork in ino 1262122887 claims free block 78882756
imap claims in-use inode 1262122887 is free, correcting imap
data fork in ino 1262122888 claims free block 78882757
data fork in ino 1262122888 claims free block 78882758
data fork in ino 1262122888 claims free block 78882759
data fork in ino 1262122888 claims free block 78882760
imap claims in-use inode 1262122888 is free, correcting imap
data fork in ino 1262122889 claims free block 78882761
imap claims in-use inode 1262122889 is free, correcting imap
data fork in ino 1262122890 claims free block 78882762
data fork in ino 1262122890 claims free block 78882763
[...]
data fork in ino 1262328055 claims free block 78897728
data fork in ino 1262328055 claims free block 78897729
data fork in ino 1262328055 claims free block 78897730
imap claims in-use inode 1262328055 is free, correcting imap
data fork in ino 1262328056 claims free block 78896726
imap claims in-use inode 1262328056 is free, correcting imap
data fork in ino 1262328057 claims free block 78896729
imap claims in-use inode 1262328057 is free, correcting imap
imap claims in-use inode 1262328058 is free, correcting imap
imap claims in-use inode 1262328059 is free, correcting imap
imap claims in-use inode 1262328060 is free, correcting imap
imap claims in-use inode 1262328061 is free, correcting imap
imap claims in-use inode 1262328062 is free, correcting imap
imap claims in-use inode 1262328063 is free, correcting imap
imap claims in-use inode 1262328064 is free, correcting imap
imap claims in-use inode 1262328065 is free, correcting imap
imap claims in-use inode 1262328066 is free, correcting imap
imap claims in-use inode 1262328067 is free, correcting imap
data fork in ino 1262328068 claims free block 78896727
imap claims in-use inode 1262328068 is free, correcting imap
imap claims in-use inode 1262328069 is free, correcting imap
[...]
imap claims in-use inode 1262328082 is free, correcting imap
imap claims in-use inode 1262328083 is free, correcting imap
data fork in ino 1262328084 claims free block 78896728
imap claims in-use inode 1262328084 is free, correcting imap
imap claims in-use inode 1262328085 is free, correcting imap
imap claims in-use inode 1262328086 is free, correcting imap
imap claims in-use inode 1262328087 is free, correcting imap
imap claims in-use inode 1262328088 is free, correcting imap
imap claims in-use inode 1262328089 is free, correcting imap
[hundreds of lines snipped]
imap claims in-use inode 1262594532 is free, correcting imap
imap claims in-use inode 1262594533 is free, correcting imap
imap claims in-use inode 1262594534 is free, correcting imap
imap claims in-use inode 1262594535 is free, correcting imap
        - agno = 76
        - agno = 77
        - agno = 78
        - agno = 79
        - agno = 80
        - agno = 81
correcting nblocks for inode 1359601283, was 18446744073709518081 - counted 1
data fork in ino 1359601284 claims free block 86060060
data fork in ino 1359601285 claims free block 86060061
data fork in ino 1359601286 claims free block 86060062
[thousands of lines snipped]
data fork in ino 1377359849 claims free block 86093592
data fork in ino 1377359849 claims free block 86093593
data fork in ino 1377359849 claims free block 86093594
data fork in ino 1377359849 claims free block 86093595
imap claims in-use inode 1377359849 is free, correcting imap
imap claims in-use inode 1377359850 is free, correcting imap
imap claims in-use inode 1377359851 is free, correcting imap
imap claims in-use inode 1377359852 is free, correcting imap
imap claims in-use inode 1377359853 is free, correcting imap
imap claims in-use inode 1377359854 is free, correcting imap
imap claims in-use inode 1377359855 is free, correcting imap
imap claims in-use inode 1377359856 is free, correcting imap
imap claims in-use inode 1377359857 is free, correcting imap
imap claims in-use inode 1377359858 is free, correcting imap
imap claims in-use inode 1377359859 is free, correcting imap
imap claims in-use inode 1377359860 is free, correcting imap
imap claims in-use inode 1377359861 is free, correcting imap
imap claims in-use inode 1377359862 is free, correcting imap
imap claims in-use inode 1377359863 is free, correcting imap
imap claims in-use inode 1377359864 is free, correcting imap
imap claims in-use inode 1377359865 is free, correcting imap
imap claims in-use inode 1380258203 is free, correcting imap
imap claims in-use inode 1380258204 is free, correcting imap
imap claims in-use inode 1380258205 is free, correcting imap
imap claims in-use inode 1380258206 is free, correcting imap
imap claims in-use inode 1380258207 is free, correcting imap
imap claims in-use inode 1380291297 is free, correcting imap
        - agno = 83
        - agno = 84
        - agno = 85
        - 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
        - agno = 6
        - agno = 7
        - agno = 8
        - agno = 9
        - agno = 10
        - agno = 11
        - agno = 12
        - agno = 13
        - agno = 14
        - agno = 15
        - agno = 16
        - agno = 17
        - agno = 18
        - agno = 19
        - agno = 20
        - agno = 21
        - agno = 22
        - agno = 23
        - agno = 24
        - agno = 25
        - agno = 26
        - agno = 27
        - agno = 28
        - agno = 29
        - agno = 30
        - agno = 31
        - agno = 32
        - agno = 33
        - agno = 34
        - agno = 35
        - agno = 36
        - agno = 37
        - agno = 38
        - agno = 39
        - agno = 40
        - agno = 41
        - agno = 42
        - agno = 43
        - agno = 44
        - agno = 45
        - agno = 46
        - agno = 47
        - agno = 48
entry "AT1700.SYS" in shortform directory 805306496 references free inode 
805306
498
junking entry "AT1700.SYS" in directory inode 805306496
        - agno = 49
        - agno = 50
        - agno = 51
        - agno = 52
        - agno = 53
        - agno = 54
        - agno = 55
        - agno = 56
        - agno = 57
        - agno = 58
        - agno = 59
        - agno = 60
        - agno = 61
        - agno = 62
        - agno = 63
        - agno = 64
        - agno = 65
        - agno = 66
        - agno = 67
        - agno = 68
        - agno = 69
        - agno = 70
        - agno = 71
        - agno = 72
        - agno = 73
        - agno = 74
        - agno = 75
        - agno = 76
        - agno = 77
        - agno = 78
        - agno = 79
        - agno = 80
        - agno = 81
        - agno = 82
        - agno = 83
        - agno = 84
        - agno = 85
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 / ... 
bad hash table for directory inode 1095174079 (hash value mismatch): 
rebuilding
rebuilding directory inode 1095174079
        - traversal finished ... 
        - traversing all unattached subtrees ... 
        - traversals finished ... 
        - moving disconnected inodes to lost+found ... 
Phase 7 - verify and correct link counts...
done


The strange thing is that I had to repeat xfs_repair TWO TIMES until no 
further errors were found. What gives?!


>It seems like you are on debian and probably have other packages then the
>1.0.2. Did you compile the userspace utils yourself or did you use the
>.deb files which are on the FTP site in the 1.0.2 directory?

No, I compiled it myself.

>Do you have it compiled with quotas, dmapi acls?

quotas: YES
dmapi:  NO
acl:    YES

Still any ideas?!

Thanks,

Ralf


-- 
Verkaufe Original-BMW-Raeder:                    L I N U X       .~.
http://adsl-bergs.rz.rwth-aachen.de/~rabe       The  Choice      /V\
                                                 of a  GNU      /( )\
                                                Generation      ^^-^^



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