Sponsored Content
Operating Systems Linux Red Hat DELL M910 with RedHat Linux 5.5 getting "Buffer I/O error on device sdd" Post 302547170 by dude2cool on Sunday 14th of August 2011 12:06:47 PM
Old 08-14-2011
I would hate to take a guess, without looking at the output of those commands. Also, what kind of SAN Storage array do you have and are you using any volume manager? Lvm is the native volume manager or you could use veritas.
Also these forums has always someone who can help in your timezone. Don'tworry about that Smilie. If I am not online,someone else will be able to help.
 

7 More Discussions You Might Find Interesting

1. Red Hat

"No Drives Found" error during Redhat Linux AS 4 installation

I'm trying to install Redhat LInux AS 4 update 4 on an IBM x306 series server. I keep getting following error: "No Drives Found. An error has occurred - no valid devices were found on which to create new file systems. Please check your hardware for the cause of this problem." I called IBM and... (2 Replies)
Discussion started by: pieman8080
2 Replies

2. Emergency UNIX and Linux Support

Mapping between "Pseudo name" and "Logical device ID" in powerpath with SVM changed....

Dear All, I was having powerpath 5.2 on SUN server with SVM connected to CLARIION box.Please find the following output : root # powermt display dev=all Pseudo name=emcpower3a CLARiiON ID=CK200073400372 Logical device ID=60060160685D1E004DD97FB647BFDC11 state=alive; policy=CLAROpt;... (1 Reply)
Discussion started by: Reboot
1 Replies

3. Red Hat

"if" and "then" statement is not working in RedHat

Dear experts, I'm trying to write a script to calculate the usage of Log Archive in a directory, so if it gets to a point where the directory size is 60%, then send out an FYI.. email. So if then it reaches to 80%, move the logs from that directory. I have written the script as follow but... (10 Replies)
Discussion started by: Afi_Linux
10 Replies

4. UNIX for Dummies Questions & Answers

UNIX rm -rf error "rm: cannot remove `filename' : Device or resource busy"

Hi Everyone, I am trying to remove a directory: $ rm -rf directory_name/ rm: cannot remove `directory_name/filename': Device or resource busy What does this mean, and why can't I remove these files? I already tried moving into the directory, and removing the files individually, but I... (7 Replies)
Discussion started by: Anna_Z
7 Replies

5. Solaris

"Can't open boot device" error !!

I've a Sun V440 machine, and it's running solaris 10 .. for some reason i need to install a fresh copy of solaris 10. for that i've prepared solaris 10 dvd but surprisingly i found there is no any dvd rom on this machine, so i've took a dvd rom from a V240 machine and inserted on V440. after... (3 Replies)
Discussion started by: Anti_Evil
3 Replies

6. Solaris

Repeated error - "se_hdlc: clone device must be attached before use" in /var/adm/messages

Below is the error being repeated on my Solaris 9 Sun-Fire-V890 machine. SAN team confirmed as everything is fine from their end. I did google and found that some people say its a known Oracle bug when you have Oracle 10G installed on your system but I kind of disagree with them. Please see below... (2 Replies)
Discussion started by: vikkash
2 Replies

7. SCO

NFS umount shows the "Device busy (Error 16)"

Hi there After making a backup copy of it sometimes happens that when I want to unmount an NFS indicates the error:umount: /path_mount busy: Device busy (Error 16) if I run lsoff, I can not find the process that is blocking the application. I'm using OpenServer 5.0.2c as one NFS server ... (14 Replies)
Discussion started by: flako
14 Replies
pvdata(8)						      System Manager's Manual							 pvdata(8)

NAME
pvdata - shows debugging information about a physical volume SYNOPSIS
pvdata [-a|--all] [-d|--debug] [-h|--help] [-E|--physicalextent] [-L|--logicalvolume] [-P[P]|--physicalvolume [--physicalvolume]] [-U|--uuidlist] [-V|--volumegroup] [-v[v]|--verbose [--verbose]] PhysicalVolumePath [PhysicalVolumePath...] DESCRIPTION
pvdata allows you to display the volume group descriptor array (VGDA) of PhysicalVolume in part or whole for debugging purposes. OPTIONS -a, --all Display all structures (PE, LV, PV, UUID, VG). The same as giving the -E -L -P -U -V options. -d, --debug Enables additional debugging output (if compiled with DEBUG). -E, --physicalextent Display physical extent structures. -h, --help Print a usage message on standard output and exit successfully. -L, --logicalvolume Display logical volume structures. -P, --physicalvolume Display physical volume structure in pvdisplay format. If given a second time, also display the on-disk LVM metadata locations. -U, --uuidlist Display the volume group UUID list. -v, --verbose Display verbose structure information. If given a second time, verbose runtime information about pvdata's activities are also shown. -V, --volumegroup Display volume group structure. --version Display the version and exit successfully. DIAGNOSTICS
pvdata returns an exit code of 0 for success and > 0 for error: 1 no physical volume name on command line 95 driver/module not in kernel 96 invalid O/O protocol version 97 error locking logical volume manager 99 invalid command line SEE ALSO
lvm(8), lvcreate(8), lvmdiskscan(8), pvcreate(8), vgcreate(8), AUTHOR
Heinz Mauelshagen <Linux-LVM@Sistina.com> Heinz Mauelshagen LVM TOOLS pvdata(8)
All times are GMT -4. The time now is 10:47 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy