Input Outpout Error

[Mad Unix]

[root at linux1 ~]# pvs
  /dev/sdc: read failed after 0 of 4096 at 0: Input/output error
  /dev/sde: read failed after 0 of 4096 at 0: Input/output error
  /dev/sdg: read failed after 0 of 4096 at 0: Input/output error
  /dev/sdi: read failed after 0 of 4096 at 0: Input/output error
  /dev/sdk: read failed after 0 of 4096 at 0: Input/output error
  /dev/sdm: read failed after 0 of 4096 at 0: Input/output error
  /dev/sdn: open failed: No medium found
  PV         VG         Fmt  Attr PSize  PFree
  /dev/sda2  VolGroup00 lvm2 a-   67.62G    0
[root at linux1 ~]#  fsck /dev/sdc
fsck 1.39 (29-May-2006)
e2fsck 1.39 (29-May-2006)
fsck.ext2: Device or resource busy while trying to open /dev/sdc
Filesystem mounted or opened exclusively by another program?
[root at linux1 ~]#  fsck /dev/sde
fsck 1.39 (29-May-2006)
e2fsck 1.39 (29-May-2006)
fsck.ext2: Device or resource busy while trying to open /dev/sde
Filesystem mounted or opened exclusively by another program?
[root at linux1 ~]#  fsck /dev/sdg
fsck 1.39 (29-May-2006)
e2fsck 1.39 (29-May-2006)
fsck.ext2: Device or resource busy while trying to open /dev/sdg
Filesystem mounted or opened exclusively by another program?
[root at linux1 ~]#  fsck /dev/sdm
fsck 1.39 (29-May-2006)
e2fsck 1.39 (29-May-2006)
fsck.ext2: Device or resource busy while trying to open /dev/sdm
Filesystem mounted or opened exclusively by another program?

[root at linux1 ~]# pvdisplay
  /dev/sdc: read failed after 0 of 4096 at 0: Input/output error
  /dev/sde: read failed after 0 of 4096 at 0: Input/output error
  /dev/sdg: read failed after 0 of 4096 at 0: Input/output error
  /dev/sdi: read failed after 0 of 4096 at 0: Input/output error
  /dev/sdk: read failed after 0 of 4096 at 0: Input/output error
  /dev/sdm: read failed after 0 of 4096 at 0: Input/output error
  /dev/sdn: open failed: No medium found
  --- Physical volume ---
  PV Name               /dev/sda2
  VG Name               VolGroup00
  PV Size               67.65 GB / not usable 24.47 MB
  Allocatable           yes (but full)
  PE Size (KByte)       32768
  Total PE              2164
  Free PE               0
  Allocated PE          2164
  PV UUID               CrfFe5-Utkp-qHEG-n2eo-KrMW-P1cZ-O9mUVz



On 11/6/07, Ben Scott <mailvortex at gmail.com> wrote:
>
> On 11/6/07, Cathy Reaves <cathy.reaves at gmail.com> wrote:
> > Why wouldn't fsck run?  And isn't that the purpose of fsck - to fix
> errors
> > such as this?
>
> The purpose of fsck is to detect and repair problems in a
> filesystem's logical structure.  It is not aware of, nor will it do
> anything to fix, problems at the LVM or block device layer.
>
> fsck might be useful for trying to recover a filesystem damaged due
> to LVM corruption, *after* LVM has been fixed.  But doing so before
> the underling storage is fixed will, at best, accomplish nothing.  It
> could even make things worse.  If you have a missing volume that could
> be brought back online, but you run fsck first, fsck will generally
> remove all the references to information that was stored on the
> missing volume.
>
> > With I/O errors, there is clearly a problem with the file system.
>
> No.  Problems with the filesystem will generally result in errors
> from the filesystem driver.  "Input/output errors" generally come from
> the block device layer.
>
> -- Ben
>
> _______________________________________________
> Linux-PowerEdge mailing list
> Linux-PowerEdge at dell.com
> http://lists.us.dell.com/mailman/listinfo/linux-poweredge
> Please read the FAQ at http://lists.us.dell.com/faq
>



-- 
madunix
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.us.dell.com/pipermail/linux-poweredge/attachments/20071107/7d7dc9bd/attachment-0001.htm