Dag-Erling Smørgrav wrote:
Miroslav Lachman000.f...@quip.cz writes:
Dag-Erling Smørgravd...@des.no writes:
Uh, 79725167 - 63 = 79725104 and 79725104 - 39845888 = 39879216. How
did you arrive at 39879105?
I am sorry, it was my confusion.
My calculation was for *LBA=79725056* reported in
Gary Jennejohn wrote:
On Wed, 17 Mar 2010 12:41:33 +0100
Miroslav Lachman000.f...@quip.cz wrote:
I absolutely don't understand how you get the number 4 (it is some magic
for me :]) but it works!
[...]
Umm, it's standard C code: 1 2 = 4. It's a power of 2, in this
case 2 squared.
I am
Miroslav Lachman 000.f...@quip.cz writes:
As you can see, there are really two different numbers LBA=79725056 in
messages and LBA = 0x04c0826f = 79725167 in SMART log.
I don't know how comfortable you are reading kernel code, but I would
suggest looking through the atadisk driver to see why the
On Thursday 18 March 2010 12:11:07 Dag-Erling Smørgrav wrote:
And if you're comfortable *writing* kernel code, I would suggest
implementing WORF in geom_mirror :)
I am intrigued, what is this WORF you speak of?
Google says it's a certain character from a popular sci-fi show...
- Pieter
Dag-Erling Smørgrav wrote:
Miroslav Lachman000.f...@quip.cz writes:
As you can see, there are really two different numbers LBA=79725056 in
messages and LBA = 0x04c0826f = 79725167 in SMART log.
I don't know how comfortable you are reading kernel code, but I would
suggest looking through the
Pieter de Goeje pie...@degoeje.nl writes:
Dag-Erling Smørgrav d...@des.no writes:
And if you're comfortable *writing* kernel code, I would suggest
implementing WORF in geom_mirror :)
I am intrigued, what is this WORF you speak of?
Write On Read Failure. It means that if you can't read a
Miroslav Lachman 000.f...@quip.cz writes:
As I write in my first post to this thread, I already tried fsdb +
findblk, but without success. Findblk did not returned any inode.
Maybe the meaning of block is of different size or something else I
can't understand.
AFAICT, block is a disk block
Dag-Erling Smørgrav wrote:
Miroslav Lachman000.f...@quip.cz writes:
The LBA of bad sector is *79725167* [...] s1 starts 63 sectors from
the beginning of the drive and /var/db has offset 39845888. So am I
right that I need to find block number *39879105* by findblk command?
Uh, 79725167 -
Gary Jennejohn wrote:
On Sun, 14 Mar 2010 17:18:45 +0100
Miroslav Lachman000.f...@quip.cz wrote:
Gary Jennejohn wrote:
On Sun, 14 Mar 2010 10:55:19 +0100
Miroslav Lachman000.f...@quip.cz wrote:
[big snip]
fsdb (inum: 3) blocks
Blocks for inode 3:
Direct blocks:
3001 (1 frag)
fsdb
Miroslav Lachman 000.f...@quip.cz writes:
Dag-Erling Smørgrav d...@des.no writes:
Uh, 79725167 - 63 = 79725104 and 79725104 - 39845888 = 39879216. How
did you arrive at 39879105?
I am sorry, it was my confusion.
My calculation was for *LBA=79725056* reported in messages:
ad4: FAILURE -
On Wed, 17 Mar 2010 12:41:33 +0100
Miroslav Lachman 000.f...@quip.cz wrote:
I absolutely don't understand how you get the number 4 (it is some magic
for me :]) but it works!
fsdb (inum: 3) blocks
Blocks for inode 3:
Direct blocks:
3001 (1 frag)
3001 * 4 = 12004
fsdb (inum: 3)
Dag-Erling Smørgrav wrote:
Miroslav Lachman000.f...@quip.cz writes:
So... can somebody with enough knowledge write some docs / script how
to find the affected file based on LBA read error from messages /
SMART log?
ZFS will tell you straight away, but I guess if you used ZFS, you
wouldn't be
On Sun, 14 Mar 2010 10:55:19 +0100
Miroslav Lachman 000.f...@quip.cz wrote:
[big snip]
fsdb (inum: 3) blocks
Blocks for inode 3:
Direct blocks:
3001 (1 frag)
fsdb (inum: 3) findblk 3001
fsdb (inum: 3)
findblk did not returned inode 3!
This is almost
Gary Jennejohn wrote:
On Sun, 14 Mar 2010 10:55:19 +0100
Miroslav Lachman000.f...@quip.cz wrote:
[big snip]
fsdb (inum: 3) blocks
Blocks for inode 3:
Direct blocks:
3001 (1 frag)
fsdb (inum: 3) findblk 3001
fsdb (inum: 3)
findblk did not returned inode 3!
This
On Sun, 14 Mar 2010 17:18:45 +0100
Miroslav Lachman 000.f...@quip.cz wrote:
Gary Jennejohn wrote:
On Sun, 14 Mar 2010 10:55:19 +0100
Miroslav Lachman000.f...@quip.cz wrote:
[big snip]
fsdb (inum: 3) blocks
Blocks for inode 3:
Direct blocks:
3001 (1 frag)
fsdb (inum: 3)
Dag-Erling Smørgrav wrote:
Miroslav Lachman000.f...@quip.cz writes:
Yes, rewriting by dd or any other way works for reallocating or
clearing pending sectors counter, but in server environment
In a server environment, you'd be a fool not to have some sort of
redundancy set up.
I am using
Miroslav Lachman 000.f...@quip.cz writes:
So... can somebody with enough knowledge write some docs / script how
to find the affected file based on LBA read error from messages /
SMART log?
ZFS will tell you straight away, but I guess if you used ZFS, you
wouldn't be asking :)
For FFS, you can
On Mon, 08.03.2010 at 13:09:19 +0200, Eugene Dzhurinsky wrote:
On Mon, Mar 08, 2010 at 12:52:43PM +0200, Eugene Dzhurinsky wrote:
dd if=/dev/ad4 of=/dev/null skip=222342559 bs=512 count=1
dd: /dev/ad4: Input/output error
0+0 records in
0+0 records out
0 bytes transferred in 2.351940
Miroslav Lachman 000.f...@quip.cz writes:
Yes, rewriting by dd or any other way works for reallocating or
clearing pending sectors counter, but in server environment
In a server environment, you'd be a fool not to have some sort of
redundancy set up.
I need to know the affected file, as it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11.03.2010 16:21, Dag-Erling Smørgrav wrote:
Miroslav Lachman 000.f...@quip.cz writes:
Yes, rewriting by dd or any other way works for reallocating or
clearing pending sectors counter, but in server environment
In a server environment, you'd
Hello, all!
Recently I've started to see the following logs in messages:
Mar 8 12:00:24 localhost smartd[795]: Device: /dev/ad4, 2 Currently unreadable
(pending) sectors
Mar 8 12:00:24 localhost smartd[795]: Device: /dev/ad4, 2 Offline
uncorrectable sectors
smartctl did really show that
Eugeny N Dzhurinsky wrote:
Recently I've started to see the following logs in messages:
Mar 8 12:00:24 localhost smartd[795]: Device: /dev/ad4, 2 Currently
unreadable (pending) sectors
Mar 8 12:00:24 localhost smartd[795]: Device: /dev/ad4, 2 Offline
uncorrectable sectors
smartctl
In message 20100308102918.ga5...@localhost, Eugeny N Dzhurinsky writes:
Now can I find out which file owns the LBAs 222342557 and 222342559 ?
How do I force remapping of these sectors? I assume that I have to write
something directly to the sectors?
I would suggest you boot single-user and run
On Mon, Mar 08, 2010 at 12:31:24PM +0200, Alexander Motin wrote:
You may try to overwrite these sectors with dd. It should trigger sector
reallocation. To be sure, you may read them before and after the write.
dd if=/dev/ad4 of=/dev/null skip=222342559 bs=512 count=1
dd: /dev/ad4: Input/output
On Mon, Mar 08, 2010 at 10:51:22AM +, Poul-Henning Kamp wrote:
I would suggest you boot single-user and run
mdmfs -s 1m md /tmp
recoverdisk -w /tmp/_.wl /dev/ad4 /dev/ad4
That will find out how many bad sectors you have and try to recover
the contents of them if possible,
On Mon, Mar 08, 2010 at 12:52:43PM +0200, Eugene Dzhurinsky wrote:
dd if=/dev/ad4 of=/dev/null skip=222342559 bs=512 count=1
dd: /dev/ad4: Input/output error
0+0 records in
0+0 records out
0 bytes transferred in 2.351940 secs (0 bytes/sec)
dd if=/dev/zero of=/dev/ad4 seek=222342559 bs=512
Eugeny N Dzhurinsky wrote:
Hello, all!
Recently I've started to see the following logs in messages:
Mar 8 12:00:24 localhost smartd[795]: Device: /dev/ad4, 2 Currently unreadable
(pending) sectors
Mar 8 12:00:24 localhost smartd[795]: Device: /dev/ad4, 2 Offline
uncorrectable sectors
On Mon, 8 Mar 2010, Miroslav Lachman wrote:
Eugeny N Dzhurinsky wrote:
Hello, all!
Recently I've started to see the following logs in messages:
Mar 8 12:00:24 localhost smartd[795]: Device: /dev/ad4, 2 Currently
unreadable (pending) sectors
Mar 8 12:00:24 localhost smartd[795]:
On Mon, Mar 08, 2010 at 12:21:44PM +0100, Miroslav Lachman wrote:
Eugeny N Dzhurinsky wrote:
We have this problem from time to time on bunch of machines. As we are
using gmirror, the easiest way is to force re-synchronization (rewrite)
of the whole drive. The problem is when there are
Eugene Dzhurinsky wrote:
On Mon, Mar 08, 2010 at 12:21:44PM +0100, Miroslav Lachman wrote:
Eugeny N Dzhurinsky wrote:
We have this problem from time to time on bunch of machines. As we are
using gmirror, the easiest way is to force re-synchronization (rewrite)
of the whole drive. The problem is
08.03.2010 13:29, Eugeny N Dzhurinsky пишет:
Hello, all!
Recently I've started to see the following logs in messages:
Mar 8 12:00:24 localhost smartd[795]: Device: /dev/ad4, 2 Currently unreadable
(pending) sectors
Mar 8 12:00:24 localhost smartd[795]: Device: /dev/ad4, 2 Offline
31 matches
Mail list logo
