* Errors reported with dmesg using reiser4
@ 2005-01-25 20:28 smallwood
2005-01-31 20:44 ` Alex Zarochentsev
0 siblings, 1 reply; 6+ messages in thread
From: smallwood @ 2005-01-25 20:28 UTC (permalink / raw)
To: reiserfs-list
Hello, for the record, this is from a system running the following specs:
Gentoo Linux
2.6.10-gentoo-r6 patched with reiser4-for-2.6.10-1
3ware 7000 series card with 4 SATA 250GB Western Digitial Drives with no
raid configured.
I am running a test pushing millions of directories onto one of the drives
using a UUID as the directory name. These all reside in the base
directory of the filesystem.
The directories are now being propogated by two python scripts creating
random data inside these folders on two of the other drives. When about
1.5gb has collected, they begin moving the folders onto the main drive.
This latest test was started last Thursday, with the drive being about 34
GBs full of data from related testing.
Since then, the drive has filled to 92GB, but at some point, I discovered
the following error:
reiser4[mv(28692)]: key_warning (fs/reiser4/plugin/object.c:97)[nikita-717]:
WARNING: Error for inode 215673251 (-2)
reiser4[mv(28692)]: write_sd_by_inode_common
(fs/reiser4/plugin/object.c:480[nikita-2221]:
WARNING: Failed to save sd for 215673251: -2
These messages are then repeated nine times.
Any suggestions on further checks I can make?
Thank You,
Nicolas Smallwood
smallwood@maya.com
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Errors reported with dmesg using reiser4
2005-01-25 20:28 smallwood
@ 2005-01-31 20:44 ` Alex Zarochentsev
0 siblings, 0 replies; 6+ messages in thread
From: Alex Zarochentsev @ 2005-01-31 20:44 UTC (permalink / raw)
To: smallwood; +Cc: reiserfs-list
Hello,
On Tue, Jan 25, 2005 at 03:28:54PM -0500, smallwood@maya.com wrote:
> Hello, for the record, this is from a system running the following specs:
>
> Gentoo Linux
> 2.6.10-gentoo-r6 patched with reiser4-for-2.6.10-1
> 3ware 7000 series card with 4 SATA 250GB Western Digitial Drives with no
> raid configured.
>
> I am running a test pushing millions of directories onto one of the drives
> using a UUID as the directory name. These all reside in the base
> directory of the filesystem.
>
> The directories are now being propogated by two python scripts creating
> random data inside these folders on two of the other drives. When about
> 1.5gb has collected, they begin moving the folders onto the main drive.
>
> This latest test was started last Thursday, with the drive being about 34
> GBs full of data from related testing.
>
> Since then, the drive has filled to 92GB, but at some point, I discovered
> the following error:
>
> reiser4[mv(28692)]: key_warning (fs/reiser4/plugin/object.c:97)[nikita-717]:
> WARNING: Error for inode 215673251 (-2)
> reiser4[mv(28692)]: write_sd_by_inode_common
> (fs/reiser4/plugin/object.c:480[nikita-2221]:
> WARNING: Failed to save sd for 215673251: -2
>
> These messages are then repeated nine times.
>
> Any suggestions on further checks I can make?
can you run fsck.reiser4 --check on that drive?
>
> Thank You,
>
> Nicolas Smallwood
> smallwood@maya.com
--
Alex.
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: Errors reported with dmesg using reiser4
[not found] <CMEFJOIJPCAMFCEKIEOEIEMICFAA.smallwood@maya.com>
@ 2005-02-01 16:55 ` Nicolas Smallwood
2005-02-02 18:15 ` Nicolas Smallwood
0 siblings, 1 reply; 6+ messages in thread
From: Nicolas Smallwood @ 2005-02-01 16:55 UTC (permalink / raw)
To: reiser
The fsck.reiser4 check reported one fatal error in the superblock
Running fsck.reiser4 --build-sb as I type this.
Nicolas Smallwood
-----Original Message-----
From: Alex Zarochentsev [mailto:zam@namesys.com]
Sent: Monday, January 31, 2005 3:44 PM
To: smallwood@maya.com
Cc: reiserfs-list@namesys.com
Subject: Re: Errors reported with dmesg using reiser4
Hello,
On Tue, Jan 25, 2005 at 03:28:54PM -0500, smallwood@maya.com wrote:
> Hello, for the record, this is from a system running the following specs:
>
> Gentoo Linux
> 2.6.10-gentoo-r6 patched with reiser4-for-2.6.10-1
> 3ware 7000 series card with 4 SATA 250GB Western Digitial Drives with no
> raid configured.
>
> I am running a test pushing millions of directories onto one of the drives
> using a UUID as the directory name. These all reside in the base
> directory of the filesystem.
>
> The directories are now being propogated by two python scripts creating
> random data inside these folders on two of the other drives. When about
> 1.5gb has collected, they begin moving the folders onto the main drive.
>
> This latest test was started last Thursday, with the drive being about 34
> GBs full of data from related testing.
>
> Since then, the drive has filled to 92GB, but at some point, I discovered
> the following error:
>
> reiser4[mv(28692)]: key_warning
(fs/reiser4/plugin/object.c:97)[nikita-717]:
> WARNING: Error for inode 215673251 (-2)
> reiser4[mv(28692)]: write_sd_by_inode_common
> (fs/reiser4/plugin/object.c:480[nikita-2221]:
> WARNING: Failed to save sd for 215673251: -2
>
> These messages are then repeated nine times.
>
> Any suggestions on further checks I can make?
can you run fsck.reiser4 --check on that drive?
>
> Thank You,
>
> Nicolas Smallwood
> smallwood@maya.com
--
Alex.
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: Errors reported with dmesg using reiser4
2005-02-01 16:55 ` Errors reported with dmesg using reiser4 Nicolas Smallwood
@ 2005-02-02 18:15 ` Nicolas Smallwood
2005-02-09 15:29 ` Nicolas Smallwood
0 siblings, 1 reply; 6+ messages in thread
From: Nicolas Smallwood @ 2005-02-02 18:15 UTC (permalink / raw)
To: reiser
Here is the output from check and build-sb
joshuadev root # fsck.reiser4 --check /dev/sdc1
*******************************************************************
This is an EXPERIMENTAL version of fsck.reiser4. Read README first.
*******************************************************************
Fscking the /dev/sdc1 block device.
Will check the consistency of the Reiser4 SuperBlock.
Will check the consistency of the Reiser4 FileSystem.
Continue?
(Yes/No): yes
***** fsck.reiser4 started at Mon Jan 31 23:38:48 2005
Fatal: Failed to open the reiser4 backup.
Fatal: Cannot open the FileSystem on (/dev/sdc1).
1 fatal corruptions were detected in SuperBlock. Run with --build-sb option
to fix them.
joshuadev root # fsck.reiser4 --build-sb /dev/sdc1
*******************************************************************
This is an EXPERIMENTAL version of fsck.reiser4. Read README first.
*******************************************************************
Fscking the /dev/sdc1 block device.
Will build the Reiser4 SuperBlock.
Will check the consistency of the Reiser4 FileSystem.
Continue?
(Yes/No): yes
***** fsck.reiser4 started at Mon Jan 31 23:40:09 2005
Enter the key plugin name [key_large]:
Reiser4 fs was detected on /dev/sdc1.
Master super block (16):
magic: ReIsEr4
blksize: 4096
format: 0x0 (format40)
label: <none>
Format super block (17):
plugin: format40
description: Disk-format for reiser4.
magic: ReIsEr40FoRmAt
flushes: 0
mkfs id: 0x73665e9a
blocks: 61049000
free blocks: 34231800
root block: 25269822
tail policy: 0x2 (smart)
next oid: 0x1c4f4d11
file count: 474893555
tree height: 5
key policy: LARGE
CHECKING STORAGE TREE
FSCK: Node (26425112), items (4) and (5): Wrong order of keys.
FSCK: Node (26425112): the node is broken. Pointed from the node (26764690),
item (64), unit (0). The whole subtree is skipped.
Read nodes 26805778
Nodes left in the tree 26805777
Leaves of them 26490907, Twigs of them 311160
Broken of them 1
Leaves of them 0, Twigs of them 0
Time interval: Mon Jan 31 23:40:28 2005 - Tue Feb 1 09:33:30 2005
CHECKING EXTENT REGIONS.
Read twigs 311160
Time interval: Tue Feb 1 09:33:30 2005 - Tue Feb 1 10:01:39 2005
Warn : Fatal corruptions were found. Semantic pass is skipped.
***** fsck.reiser4 finished at Tue Feb 1 10:01:39 2005
Closing fs...done
1 fatal corruptions were detected in FileSystem. Run with --build-fs option
to fix them.
***************************************
Running build-fs now...
Thanks,
Nicolas Smallwood
-----Original Message-----
From: Nicolas Smallwood [mailto:smallwood@maya.com]
Sent: Tuesday, February 01, 2005 11:56 AM
To: reiser
Subject: RE: Errors reported with dmesg using reiser4
The fsck.reiser4 check reported one fatal error in the superblock
Running fsck.reiser4 --build-sb as I type this.
Nicolas Smallwood
-----Original Message-----
From: Alex Zarochentsev [mailto:zam@namesys.com]
Sent: Monday, January 31, 2005 3:44 PM
To: smallwood@maya.com
Cc: reiserfs-list@namesys.com
Subject: Re: Errors reported with dmesg using reiser4
Hello,
On Tue, Jan 25, 2005 at 03:28:54PM -0500, smallwood@maya.com wrote:
> Hello, for the record, this is from a system running the following specs:
>
> Gentoo Linux
> 2.6.10-gentoo-r6 patched with reiser4-for-2.6.10-1
> 3ware 7000 series card with 4 SATA 250GB Western Digitial Drives with no
> raid configured.
>
> I am running a test pushing millions of directories onto one of the drives
> using a UUID as the directory name. These all reside in the base
> directory of the filesystem.
>
> The directories are now being propogated by two python scripts creating
> random data inside these folders on two of the other drives. When about
> 1.5gb has collected, they begin moving the folders onto the main drive.
>
> This latest test was started last Thursday, with the drive being about 34
> GBs full of data from related testing.
>
> Since then, the drive has filled to 92GB, but at some point, I discovered
> the following error:
>
> reiser4[mv(28692)]: key_warning
(fs/reiser4/plugin/object.c:97)[nikita-717]:
> WARNING: Error for inode 215673251 (-2)
> reiser4[mv(28692)]: write_sd_by_inode_common
> (fs/reiser4/plugin/object.c:480[nikita-2221]:
> WARNING: Failed to save sd for 215673251: -2
>
> These messages are then repeated nine times.
>
> Any suggestions on further checks I can make?
can you run fsck.reiser4 --check on that drive?
>
> Thank You,
>
> Nicolas Smallwood
> smallwood@maya.com
--
Alex.
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: Errors reported with dmesg using reiser4
2005-02-02 18:15 ` Nicolas Smallwood
@ 2005-02-09 15:29 ` Nicolas Smallwood
2005-02-09 15:37 ` Nicolas Smallwood
0 siblings, 1 reply; 6+ messages in thread
From: Nicolas Smallwood @ 2005-02-09 15:29 UTC (permalink / raw)
To: reiser
And the fsck.reiser4 --build-fs is done
Is there anything further I could provide to help in gleaning usefulness
from this data?
Thanks,
Nicolas Smallwood
***** fsck.reiser4 started at Wed Feb 2 04:04:20 2005
Reiser4 fs was detected on /dev/sdc1.
Master super block (16):
magic: ReIsEr4
blksize: 4096
format: 0x0 (format40)
label: <none>
Format super block (17):
plugin: format40
description: Disk-format for reiser4.
magic: ReIsEr40FoRmAt
flushes: 0
mkfs id: 0x73665e9a
blocks: 61049000
free blocks: 34231800
root block: 25269822
tail policy: 0x2 (smart)
next oid: 0x1c4f4d11
file count: 474893555
tree height: 5
key policy: LARGE
CHECKING STORAGE TREE
FSCK: Node (26425112), items (4) and (5): Wrong order of keys.
FSCK: Node (26425112): the node is unrecoverable. Pointed from the node
(26764690), item (64), unit (0). Removed.
Read nodes 26805778
Nodes left in the tree 26805777
Leaves of them 26490907, Twigs of them 311160
Emptied of them 1
Leaves of them 0, Twigs of them 0
Time interval: Wed Feb 2 04:04:36 2005 - Wed Feb 2 16:22:35 2005
CHECKING EXTENT REGIONS.
Read twigs 311160
Time interval: Wed Feb 2 16:22:35 2005 - Wed Feb 2 16:50:50 2005
LOOKING FOR UNCONNECTED NODES
FSCK: Node (24599401), items (31) and (32): Wrong order of keys.
FSCK: Node (26683237), items (8) and (9): Wrong order of keys.
Read nodes 6717
Good nodes 6715
Leaves of them 6628, Twigs of them 87
Time interval: Wed Feb 2 16:50:56 2005 - Wed Feb 2 16:51:18 2005
CHECKING EXTENT REGIONS.
Read twigs 87
Time interval: Wed Feb 2 16:51:18 2005 - Wed Feb 2 16:51:18 2005
INSERTING UNCONNECTED NODES
1. Twigs: done
2. Twigs by item: done
3. Leaves: done
4. Leaves by item: done
Twigs: read 87, inserted 0, by item 0, empty 87
Leaves: read 6628, inserted 6499, by item 129
Time interval: Wed Feb 2 16:51:23 2005 - Wed Feb 2 16:51:42 2005
CHECKING SEMANTIC TREE
FSCK: No 'lost+found' entry found. Building a new object with the key
2a:0:ffff.
FSCK: Failed to recognize the plugin for the directory [2a:0:ffff].
FSCK: Trying to recover the directory [2a:0:ffff] with the default
plugin--dir40.
FSCK: The file [2a:0:ffff] does not have a StatData item. Creating a new
one. Plugin dir40.
FSCK: Directory [2a:0:ffff]: The entry "." is not found. Insert a new one.
Plugin (dir40).
FSCK: Node (10989093), item (2), [2a:0:ffff] (stat40): wrong size (0), Fixed
to (1).
FSCK: Node (10989093), item (2), [2a:0:ffff] (stat40): wrong bytes (0),
Fixed to (50).
FSCK: Node (10989093), item (6), [2a:16a6f736875615f:10007] (stat40): wrong
size (59361986), Fixed to (59361981).
FSCK: Node (10989093), item (6), [2a:16a6f736875615f:10007] (stat40): wrong
bytes (5105132048), Fixed to (5105131618).
FSCK: Node (24084), item (11), [10007:17e303161353238:cdae9a3] (stat40):
wrong size (2), Fixed to (9).
FSCK: Node (24084), item (11), [10007:17e303161353238:cdae9a3] (stat40):
wrong bytes (100), Fixed to (450).
Found 474893557 objects.
Lost&found 5 objects.
Time interval: Wed Feb 2 16:51:42 2005 - Tue Feb 8 04:56:47 2005
CLEANUPING STORAGE TREE
Removed items 0
Time interval: Tue Feb 8 04:56:48 2005 - Tue Feb 8 19:19:45 2005
FSCK: File count 474893555 is wrong. Fixed to 474893557.
***** fsck.reiser4 finished at Tue Feb 8 19:19:45 2005
Closing fs...done
Nicolas Smallwood
Maya Design, Inc
Suite 702
2100 Wharton Street
Pittsburgh, PA 15203
412-488-2900 (voice)
412-488-2940 (fax)
-----Original Message-----
From: Nicolas Smallwood [mailto:smallwood@maya.com]
Sent: Wednesday, February 02, 2005 1:15 PM
To: reiser
Subject: RE: Errors reported with dmesg using reiser4
Here is the output from check and build-sb
joshuadev root # fsck.reiser4 --check /dev/sdc1
*******************************************************************
This is an EXPERIMENTAL version of fsck.reiser4. Read README first.
*******************************************************************
Fscking the /dev/sdc1 block device.
Will check the consistency of the Reiser4 SuperBlock.
Will check the consistency of the Reiser4 FileSystem.
Continue?
(Yes/No): yes
***** fsck.reiser4 started at Mon Jan 31 23:38:48 2005
Fatal: Failed to open the reiser4 backup.
Fatal: Cannot open the FileSystem on (/dev/sdc1).
1 fatal corruptions were detected in SuperBlock. Run with --build-sb option
to fix them.
joshuadev root # fsck.reiser4 --build-sb /dev/sdc1
*******************************************************************
This is an EXPERIMENTAL version of fsck.reiser4. Read README first.
*******************************************************************
Fscking the /dev/sdc1 block device.
Will build the Reiser4 SuperBlock.
Will check the consistency of the Reiser4 FileSystem.
Continue?
(Yes/No): yes
***** fsck.reiser4 started at Mon Jan 31 23:40:09 2005
Enter the key plugin name [key_large]:
Reiser4 fs was detected on /dev/sdc1.
Master super block (16):
magic: ReIsEr4
blksize: 4096
format: 0x0 (format40)
label: <none>
Format super block (17):
plugin: format40
description: Disk-format for reiser4.
magic: ReIsEr40FoRmAt
flushes: 0
mkfs id: 0x73665e9a
blocks: 61049000
free blocks: 34231800
root block: 25269822
tail policy: 0x2 (smart)
next oid: 0x1c4f4d11
file count: 474893555
tree height: 5
key policy: LARGE
CHECKING STORAGE TREE
FSCK: Node (26425112), items (4) and (5): Wrong order of keys.
FSCK: Node (26425112): the node is broken. Pointed from the node (26764690),
item (64), unit (0). The whole subtree is skipped.
Read nodes 26805778
Nodes left in the tree 26805777
Leaves of them 26490907, Twigs of them 311160
Broken of them 1
Leaves of them 0, Twigs of them 0
Time interval: Mon Jan 31 23:40:28 2005 - Tue Feb 1 09:33:30 2005
CHECKING EXTENT REGIONS.
Read twigs 311160
Time interval: Tue Feb 1 09:33:30 2005 - Tue Feb 1 10:01:39 2005
Warn : Fatal corruptions were found. Semantic pass is skipped.
***** fsck.reiser4 finished at Tue Feb 1 10:01:39 2005
Closing fs...done
1 fatal corruptions were detected in FileSystem. Run with --build-fs option
to fix them.
***************************************
Running build-fs now...
Thanks,
Nicolas Smallwood
-----Original Message-----
From: Nicolas Smallwood [mailto:smallwood@maya.com]
Sent: Tuesday, February 01, 2005 11:56 AM
To: reiser
Subject: RE: Errors reported with dmesg using reiser4
The fsck.reiser4 check reported one fatal error in the superblock
Running fsck.reiser4 --build-sb as I type this.
Nicolas Smallwood
-----Original Message-----
From: Alex Zarochentsev [mailto:zam@namesys.com]
Sent: Monday, January 31, 2005 3:44 PM
To: smallwood@maya.com
Cc: reiserfs-list@namesys.com
Subject: Re: Errors reported with dmesg using reiser4
Hello,
On Tue, Jan 25, 2005 at 03:28:54PM -0500, smallwood@maya.com wrote:
> Hello, for the record, this is from a system running the following specs:
>
> Gentoo Linux
> 2.6.10-gentoo-r6 patched with reiser4-for-2.6.10-1
> 3ware 7000 series card with 4 SATA 250GB Western Digitial Drives with no
> raid configured.
>
> I am running a test pushing millions of directories onto one of the drives
> using a UUID as the directory name. These all reside in the base
> directory of the filesystem.
>
> The directories are now being propogated by two python scripts creating
> random data inside these folders on two of the other drives. When about
> 1.5gb has collected, they begin moving the folders onto the main drive.
>
> This latest test was started last Thursday, with the drive being about 34
> GBs full of data from related testing.
>
> Since then, the drive has filled to 92GB, but at some point, I discovered
> the following error:
>
> reiser4[mv(28692)]: key_warning
(fs/reiser4/plugin/object.c:97)[nikita-717]:
> WARNING: Error for inode 215673251 (-2)
> reiser4[mv(28692)]: write_sd_by_inode_common
> (fs/reiser4/plugin/object.c:480[nikita-2221]:
> WARNING: Failed to save sd for 215673251: -2
>
> These messages are then repeated nine times.
>
> Any suggestions on further checks I can make?
can you run fsck.reiser4 --check on that drive?
>
> Thank You,
>
> Nicolas Smallwood
> smallwood@maya.com
--
Alex.
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: Errors reported with dmesg using reiser4
2005-02-09 15:29 ` Nicolas Smallwood
@ 2005-02-09 15:37 ` Nicolas Smallwood
0 siblings, 0 replies; 6+ messages in thread
From: Nicolas Smallwood @ 2005-02-09 15:37 UTC (permalink / raw)
To: reiser
In an interesting twist:
I just mounted the filesystem after running --build-fs.
It seems to mount just fine, but dmesg reports the following error:
"Warning, mounting filesystem with fatal errors, forcing read-only mount"
I unmounted the drive and tried again, with the same error. What is
interesting
is that the drive is in fact mounted writable, as I was able to add files,
unmount,
remount the disk to reopen them. The original data is still on the drive as
well,
so am I safe to assume this is an ignorable case?
Thanks,
Nicolas Smallwood
-----Original Message-----
From: Nicolas Smallwood [mailto:smallwood@maya.com]
Sent: Wednesday, February 09, 2005 10:30 AM
To: reiser
Subject: RE: Errors reported with dmesg using reiser4
And the fsck.reiser4 --build-fs is done
Is there anything further I could provide to help in gleaning usefulness
from this data?
Thanks,
Nicolas Smallwood
***** fsck.reiser4 started at Wed Feb 2 04:04:20 2005
Reiser4 fs was detected on /dev/sdc1.
Master super block (16):
magic: ReIsEr4
blksize: 4096
format: 0x0 (format40)
label: <none>
Format super block (17):
plugin: format40
description: Disk-format for reiser4.
magic: ReIsEr40FoRmAt
flushes: 0
mkfs id: 0x73665e9a
blocks: 61049000
free blocks: 34231800
root block: 25269822
tail policy: 0x2 (smart)
next oid: 0x1c4f4d11
file count: 474893555
tree height: 5
key policy: LARGE
CHECKING STORAGE TREE
FSCK: Node (26425112), items (4) and (5): Wrong order of keys.
FSCK: Node (26425112): the node is unrecoverable. Pointed from the node
(26764690), item (64), unit (0). Removed.
Read nodes 26805778
Nodes left in the tree 26805777
Leaves of them 26490907, Twigs of them 311160
Emptied of them 1
Leaves of them 0, Twigs of them 0
Time interval: Wed Feb 2 04:04:36 2005 - Wed Feb 2 16:22:35 2005
CHECKING EXTENT REGIONS.
Read twigs 311160
Time interval: Wed Feb 2 16:22:35 2005 - Wed Feb 2 16:50:50 2005
LOOKING FOR UNCONNECTED NODES
FSCK: Node (24599401), items (31) and (32): Wrong order of keys.
FSCK: Node (26683237), items (8) and (9): Wrong order of keys.
Read nodes 6717
Good nodes 6715
Leaves of them 6628, Twigs of them 87
Time interval: Wed Feb 2 16:50:56 2005 - Wed Feb 2 16:51:18 2005
CHECKING EXTENT REGIONS.
Read twigs 87
Time interval: Wed Feb 2 16:51:18 2005 - Wed Feb 2 16:51:18 2005
INSERTING UNCONNECTED NODES
1. Twigs: done
2. Twigs by item: done
3. Leaves: done
4. Leaves by item: done
Twigs: read 87, inserted 0, by item 0, empty 87
Leaves: read 6628, inserted 6499, by item 129
Time interval: Wed Feb 2 16:51:23 2005 - Wed Feb 2 16:51:42 2005
CHECKING SEMANTIC TREE
FSCK: No 'lost+found' entry found. Building a new object with the key
2a:0:ffff.
FSCK: Failed to recognize the plugin for the directory [2a:0:ffff].
FSCK: Trying to recover the directory [2a:0:ffff] with the default
plugin--dir40.
FSCK: The file [2a:0:ffff] does not have a StatData item. Creating a new
one. Plugin dir40.
FSCK: Directory [2a:0:ffff]: The entry "." is not found. Insert a new one.
Plugin (dir40).
FSCK: Node (10989093), item (2), [2a:0:ffff] (stat40): wrong size (0), Fixed
to (1).
FSCK: Node (10989093), item (2), [2a:0:ffff] (stat40): wrong bytes (0),
Fixed to (50).
FSCK: Node (10989093), item (6), [2a:16a6f736875615f:10007] (stat40): wrong
size (59361986), Fixed to (59361981).
FSCK: Node (10989093), item (6), [2a:16a6f736875615f:10007] (stat40): wrong
bytes (5105132048), Fixed to (5105131618).
FSCK: Node (24084), item (11), [10007:17e303161353238:cdae9a3] (stat40):
wrong size (2), Fixed to (9).
FSCK: Node (24084), item (11), [10007:17e303161353238:cdae9a3] (stat40):
wrong bytes (100), Fixed to (450).
Found 474893557 objects.
Lost&found 5 objects.
Time interval: Wed Feb 2 16:51:42 2005 - Tue Feb 8 04:56:47 2005
CLEANUPING STORAGE TREE
Removed items 0
Time interval: Tue Feb 8 04:56:48 2005 - Tue Feb 8 19:19:45 2005
FSCK: File count 474893555 is wrong. Fixed to 474893557.
***** fsck.reiser4 finished at Tue Feb 8 19:19:45 2005
Closing fs...done
Nicolas Smallwood
Maya Design, Inc
Suite 702
2100 Wharton Street
Pittsburgh, PA 15203
412-488-2900 (voice)
412-488-2940 (fax)
-----Original Message-----
From: Nicolas Smallwood [mailto:smallwood@maya.com]
Sent: Wednesday, February 02, 2005 1:15 PM
To: reiser
Subject: RE: Errors reported with dmesg using reiser4
Here is the output from check and build-sb
joshuadev root # fsck.reiser4 --check /dev/sdc1
*******************************************************************
This is an EXPERIMENTAL version of fsck.reiser4. Read README first.
*******************************************************************
Fscking the /dev/sdc1 block device.
Will check the consistency of the Reiser4 SuperBlock.
Will check the consistency of the Reiser4 FileSystem.
Continue?
(Yes/No): yes
***** fsck.reiser4 started at Mon Jan 31 23:38:48 2005
Fatal: Failed to open the reiser4 backup.
Fatal: Cannot open the FileSystem on (/dev/sdc1).
1 fatal corruptions were detected in SuperBlock. Run with --build-sb option
to fix them.
joshuadev root # fsck.reiser4 --build-sb /dev/sdc1
*******************************************************************
This is an EXPERIMENTAL version of fsck.reiser4. Read README first.
*******************************************************************
Fscking the /dev/sdc1 block device.
Will build the Reiser4 SuperBlock.
Will check the consistency of the Reiser4 FileSystem.
Continue?
(Yes/No): yes
***** fsck.reiser4 started at Mon Jan 31 23:40:09 2005
Enter the key plugin name [key_large]:
Reiser4 fs was detected on /dev/sdc1.
Master super block (16):
magic: ReIsEr4
blksize: 4096
format: 0x0 (format40)
label: <none>
Format super block (17):
plugin: format40
description: Disk-format for reiser4.
magic: ReIsEr40FoRmAt
flushes: 0
mkfs id: 0x73665e9a
blocks: 61049000
free blocks: 34231800
root block: 25269822
tail policy: 0x2 (smart)
next oid: 0x1c4f4d11
file count: 474893555
tree height: 5
key policy: LARGE
CHECKING STORAGE TREE
FSCK: Node (26425112), items (4) and (5): Wrong order of keys.
FSCK: Node (26425112): the node is broken. Pointed from the node (26764690),
item (64), unit (0). The whole subtree is skipped.
Read nodes 26805778
Nodes left in the tree 26805777
Leaves of them 26490907, Twigs of them 311160
Broken of them 1
Leaves of them 0, Twigs of them 0
Time interval: Mon Jan 31 23:40:28 2005 - Tue Feb 1 09:33:30 2005
CHECKING EXTENT REGIONS.
Read twigs 311160
Time interval: Tue Feb 1 09:33:30 2005 - Tue Feb 1 10:01:39 2005
Warn : Fatal corruptions were found. Semantic pass is skipped.
***** fsck.reiser4 finished at Tue Feb 1 10:01:39 2005
Closing fs...done
1 fatal corruptions were detected in FileSystem. Run with --build-fs option
to fix them.
***************************************
Running build-fs now...
Thanks,
Nicolas Smallwood
-----Original Message-----
From: Nicolas Smallwood [mailto:smallwood@maya.com]
Sent: Tuesday, February 01, 2005 11:56 AM
To: reiser
Subject: RE: Errors reported with dmesg using reiser4
The fsck.reiser4 check reported one fatal error in the superblock
Running fsck.reiser4 --build-sb as I type this.
Nicolas Smallwood
-----Original Message-----
From: Alex Zarochentsev [mailto:zam@namesys.com]
Sent: Monday, January 31, 2005 3:44 PM
To: smallwood@maya.com
Cc: reiserfs-list@namesys.com
Subject: Re: Errors reported with dmesg using reiser4
Hello,
On Tue, Jan 25, 2005 at 03:28:54PM -0500, smallwood@maya.com wrote:
> Hello, for the record, this is from a system running the following specs:
>
> Gentoo Linux
> 2.6.10-gentoo-r6 patched with reiser4-for-2.6.10-1
> 3ware 7000 series card with 4 SATA 250GB Western Digitial Drives with no
> raid configured.
>
> I am running a test pushing millions of directories onto one of the drives
> using a UUID as the directory name. These all reside in the base
> directory of the filesystem.
>
> The directories are now being propogated by two python scripts creating
> random data inside these folders on two of the other drives. When about
> 1.5gb has collected, they begin moving the folders onto the main drive.
>
> This latest test was started last Thursday, with the drive being about 34
> GBs full of data from related testing.
>
> Since then, the drive has filled to 92GB, but at some point, I discovered
> the following error:
>
> reiser4[mv(28692)]: key_warning
(fs/reiser4/plugin/object.c:97)[nikita-717]:
> WARNING: Error for inode 215673251 (-2)
> reiser4[mv(28692)]: write_sd_by_inode_common
> (fs/reiser4/plugin/object.c:480[nikita-2221]:
> WARNING: Failed to save sd for 215673251: -2
>
> These messages are then repeated nine times.
>
> Any suggestions on further checks I can make?
can you run fsck.reiser4 --check on that drive?
>
> Thank You,
>
> Nicolas Smallwood
> smallwood@maya.com
--
Alex.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2005-02-09 15:37 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <CMEFJOIJPCAMFCEKIEOEIEMICFAA.smallwood@maya.com>
2005-02-01 16:55 ` Errors reported with dmesg using reiser4 Nicolas Smallwood
2005-02-02 18:15 ` Nicolas Smallwood
2005-02-09 15:29 ` Nicolas Smallwood
2005-02-09 15:37 ` Nicolas Smallwood
2005-01-25 20:28 smallwood
2005-01-31 20:44 ` Alex Zarochentsev
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.