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

Freeing blocks not in datazone



These came up on dmesg this morning:

attempt to access beyond end of device
09:00: rw=0, want=1635237736, limit=976791680
attempt to access beyond end of device
09:00: rw=0, want=1635237736, limit=976791680
EXT3-fs error (device md(9,0)): ext3_free_blocks: Freeing blocks not in
datazone - block = 4293394431, count = 1
attempt to access beyond end of device
09:00: rw=0, want=1930439616, limit=976791680
attempt to access beyond end of device
09:00: rw=0, want=1930439616, limit=976791680
EXT3-fs error (device md(9,0)): ext3_free_blocks: Freeing blocks not in
datazone - block = 3703835375, count = 1

I am running RH 7.3 with 2.4.20-18.7smp and RAID 5.

Also

tune2fs 1.27 (8-Mar-2002)
Filesystem volume name:   <none>
Last mounted on:          <not available>
Filesystem UUID:          80307f32-6acd-4856-8ce4-63044f30d057
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal filetype needs_recovery
sparse_super large_file
Filesystem state:         clean with errors
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              122109952
Block count:              244197920
Reserved block count:     12209896
[....]

Can I run any other diagnostics to find out more about RAID
drive? Is e2fsck an option now? It seems I still can read/write to the
aforementioned RIAD drive without any problem.

I would appreciate any feedback. Thanks.


-Sharif





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