11-23-2016
Are these local disks or hardware protected in some way? (SAN provided, RAID device etc.)
The reason I ask is that you have a single copy of each PP. On real hardware you might lose the LV if any disk fails. If it is hardware protected, then you might be causing yourself an IO overhead by striping. I know it sounds counter-intuitive, but I've seen issues where spreading IO according to how the OS sees it can cause contention on the real disks when a SAN also spreads the IO. Bizarrely we improved IO when we tried to create hot-spots as the OS saw it because the SAN then really did spread the heavy IO properly.
Can you explain a little more about what hardware you have in play?
Thanks,
Robin
10 More Discussions You Might Find Interesting
1. AIX
Hi All,
I am new to AIX.
I need to extend one Logical Volume it is jfs type on On AIX 5.1.
I have enough free space on the volume group for this extension
Can I use smitty chjfs , will this do it without interruptions to the application that is using this Logical Volume.
Thanks
Scampi (1 Reply)
Discussion started by: scampi
1 Replies
2. UNIX for Advanced & Expert Users
Hello,
I have logical volume group of 50GB, in which I have 2 logical volumes, LogVol01 and LogVol02, both are of 10GB.
If I extend LogVol01 further by 10GB, then it keeps the extended copy after logical volume 2. I want to know where it keeps this information
Regards
Himanshu (3 Replies)
Discussion started by: ghimanshu
3 Replies
3. AIX
Hi,
Smit "Increase the Size of a Logical Volume" command failed. Output:
----------------------------------------------------------
Command: failed stdout: yes stderr: no
Before command completion, additional instructions may appear below.
The distribution of this command (111) failed on... (2 Replies)
Discussion started by: vilius
2 Replies
4. AIX
Hi!
Can anyone help me on how I can do a basic check on the Unix filesystems / physical volumes and logical volumes?
What items should I check, like where do I look at in smit? Or are there commands that I should execute?
I need to do this as I was informed by IBM that there seems to be... (1 Reply)
Discussion started by: chipahoys
1 Replies
5. AIX
Hello,
I am a french computer technician, and i speak English just a little.
On Aix 5.3, I encounter a name conflict logical volume on two volume group.
The first volume lvnode01 is OK in rootvg and mounted. It is also consistent in the ODM
root # lsvg -l rootvg |grep lvnode01 ... (10 Replies)
Discussion started by: dantares
10 Replies
6. HP-UX
Background:
# uname -a
HP-UX deedee B.11.23 U ia64 4294967295 unlimited-user license
deedee.rsn.hp.com:/
# bdf /opt
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol6 6553600 6394216 158144 98% /opt
/opt is almost full... (3 Replies)
Discussion started by: Rob Sandifer
3 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I am new to unix. I am working on Red Hat Linux and side by side on AIX also. After reading the concepts of Storage, I am now really confused regarding the terminologies
1)Physical Volume
2)Volume Group
3)Logical Volume
4)Physical Partition
Please help me to understand these concepts. (6 Replies)
Discussion started by: kashifsd17
6 Replies
8. HP-UX
Want to extend the /home filesystem:
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol4 262144 260088 2056 99% /home
root@server:./root # vgdisplay vg00
--- Volume groups ---
VG Name /dev/vg00
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 11
Open... (4 Replies)
Discussion started by: proactiveaditya
4 Replies
9. AIX
Hello everyone,
I just read that while creating a logical volume(LV) we can choose the region of the physical volume (PV) in which the LV should be created.
When I say region I mean: outer edge - outer middle - center - inner middle and inner edge.
Can anyone help me understand the utility... (11 Replies)
Discussion started by: adilyos
11 Replies
10. Red Hat
Hello Guys,
I want to create a file system dedicated for an application installation. But there is no space in volume group to create a new logical volume. There is enough space in other logical volume which is being mounted on /var.
I know we can use that logical volume and create a virtual... (2 Replies)
Discussion started by: vamshigvk475
2 Replies
LEARN ABOUT LINUX
addbadsec
addbadsec(1M) System Administration Commands addbadsec(1M)
NAME
addbadsec - map out defective disk blocks
SYNOPSIS
addbadsec [-p] [ -a blkno [blkno...]] [-f filename] raw_device
DESCRIPTION
addbadsec is used by the system administrator to map out bad disk blocks. Normally, these blocks are identified during surface analysis,
but occasionally the disk subsystem reports unrecoverable data errors indicating a bad block. A block number reported in this way can be
fed directly into addbadsec, and the block will be remapped. addbadsec will first attempt hardware remapping. This is supported on SCSI
drives and takes place at the disk hardware level. If the target is an IDE drive, then software remapping is used. In order for software
remapping to succeed, the partition must contain an alternate slice and there must be room in this slice to perform the mapping.
It should be understood that bad blocks lead to data loss. Remapping a defective block does not repair a damaged file. If a bad block
occurs to a disk-resident file system structure such as a superblock, the entire slice might have to be recovered from a backup.
OPTIONS
The following options are supported:
-a Adds the specified blocks to the hardware or software map. If more than one block number is specified, the entire list should be
quoted and block numbers should be separated by white space.
-f Adds the specified blocks to the hardware or software map. The bad blocks are listed, one per line, in the specified file.
-p Causes addbadsec to print the current software map. The output shows the defective block and the assigned alternate. This option
cannot be used to print the hardware map.
OPERANDS
The following operand is supported:
raw_device The address of the disk drive (see FILES).
FILES
The raw device should be /dev/rdsk/c?[t?]d?p0. See disks(1M) for an explanation of SCSI and IDE device naming conventions.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Architecture |x86 |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO
disks(1M), diskscan(1M), fdisk(1M), fmthard(1M), format(1M), attributes(5)
NOTES
The format(1M) utility is available to format, label, analyze, and repair SCSI disks. This utility is included with the addbadsec,
diskscan(1M), fdisk(1M), and fmthard(1M) commands available for x86. To format an IDE disk, use the DOS "format" utility; however, to
label, analyze, or repair IDE disks on x86 systems, use the Solaris format(1M) utility.
SunOS 5.10 24 Feb 1998 addbadsec(1M)