lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <OF3CD75888.312195E5-ON85257831.0050CD2F-85257831.0051875E@dart.biz>
Date:	Tue, 8 Feb 2011 09:50:31 -0500
From:	bryan.coleman@...t.biz
To:	linux-ext4@...r.kernel.org, linux-ext4-owner@...r.kernel.org
Cc:	Ted Ts'o <tytso@....edu>
Subject: Re: ext4 problems with external RAID array via SAS connection

Well, I attempted to run fsck on the problem drive using the script 
command to capture the transcript; however, it failed to read a block from 
the file system.  The exception was "fsck.ext4: Attempt to read block from 
filesystem resulted in short read while trying to open 
/dev/mapper/vg_storage-lv_storage". 

Other messages that are now in /var/log/messages:

Buffer I/O error on device dm-2, logical block 0
lost page write due to I/O error on dm-2
EXT4-fs (dm-2): previous I/O error to superblock detected
Buffer I/O error on device dm-2, logical block 0
lost page write due to I/O error on dm-2
Buffer I/O error on device dm-2, logical block 0
Buffer I/O error on device dm-2, logical block 1
Buffer I/O error on device dm-2, logical block 2
Buffer I/O error on device dm-2, logical block 3
Buffer I/O error on device dm-2, logical block 0
EXT4-fs (dm-2): unable to read superblock


Since it looks like I need to start the process all over again, is there a 
good way to quickly determine if the problem is hardware related?  Is 
there a preferred method that will stress test the drive and shed more 
light on what might be going wrong?

Thank you,

Bryan



From:   bryan.coleman@...t.biz
To:     linux-ext4@...r.kernel.org, linux-ext4-owner@...r.kernel.org
Date:   02/08/2011 08:19 AM
Subject:        Re: ext4 problems with external RAID array via SAS 
connection
Sent by:        linux-ext4-owner@...r.kernel.org



When I ran fsck after the first bout of failure, it did report a lot of 
errors.  I do not have a copy of that fsck transcript; however, I have not 

yet run fsck since my second attempt.  Is there a method of capturing the 
transcript that is preferred?

Bryan



From:   Ted Ts'o <tytso@....edu>
To:     bryan.coleman@...t.biz
Cc:     linux-ext4@...r.kernel.org
Date:   02/07/2011 05:55 PM
Subject:        Re: ext4 problems with external RAID array via SAS 
connection
Sent by:        linux-ext4-owner@...r.kernel.org



On Mon, Feb 07, 2011 at 01:53:18PM -0500, bryan.coleman@...t.biz wrote:
> I am experiencing problems with an ext4 file system.
> 
> At first, the drive seemed to work fine.  I was primarily copying things 


> to the drive migrating data from another server.  After many GBs of 
data, 
> that seemingly successfully were done being transferred, I started 
seeing 
> ext4 errors in /var/log/messages.  I then unmounted the drive and ran 
fsck 
> on it (which took multiple hours to run).  I then ls'ed around and one 
of 
> the areas caused the system to again throw ext4 errors.

Did fsck report any errors?  Do you have a copy of your fsck
transcript?

The errors you've reported do make me suspicious that there's
something unstable with your hardware...

  - Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ