Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Raid0 array stresses only 1 disk out of 3 Post 302970721 by gull04 on Monday 11th of April 2016 09:24:52 AM
Old 04-11-2016
Hi,

This could be a number of things, but it will most likely revolve around the stripe size.

Regards

Gull04
 

9 More Discussions You Might Find Interesting

1. Solaris

A1000 Disk storage array

I am new to the unix world. I have SunBlade 100 and A1000 Disk storage array with 12 Hard drives. I used SCSI card and SCSI cables to connect. When I do the format command,I can see disk storage as one disk instead of 12 disks as below. Could anybody can explain why? What should I do in order... (1 Reply)
Discussion started by: Dulasi
1 Replies

2. Solaris

Solaris RAID0 doubt...

friends, Suppose I am typing metastat command and it is showing: d100: Concat/Stripe Size: 369495 blocks (180 MB) Stripe 0: (interlace: 32 blocks) Device Start Block Dbase Reloc c1d0s0 16065 Yes Yes c1d0s1 0 No Yes... (4 Replies)
Discussion started by: saagar
4 Replies

3. UNIX for Advanced & Expert Users

3510 Disk Array Problem

I have a 3510 disk array attached to a T2000 server. The dmesg command shows disk error as follows and is generated a couple of times during the day Aug 18 03:35:51 myserver SUNWscsdMonitor: <rctrl6042> Standard General Event, CHL:2 ID:22 Drive NOTICE: Drive Recovered Error - 5F8E1F... (1 Reply)
Discussion started by: Tirmazi
1 Replies

4. Linux

Raid0 recovery from external HD

Hi, I have the Lacie Big Disk, which is a external hard drive enclosure in a hardware RAID0 array of 2x250GB disks. The RAID controller seems to have died, leaving me with 2 working hard drives but no way to get the data. I tried hooking the drives up to a windows machine and using Raid... (4 Replies)
Discussion started by: dangral
4 Replies

5. UNIX for Dummies Questions & Answers

Why is RAID0 faster?

I have read anecdotes about people installing RAID0 (RAID - Wikipedia, the free encyclopedia) on some of their machines because it gives a performance boost. Because bandwidth on the motherboard is limited, can someone explain exactly why it should be faster? (7 Replies)
Discussion started by: figaro
7 Replies

6. Solaris

Disk Array

So I have 2 solaris sun servers one with a disk array with 14 drives which I need to move to the other server. How do I move the disk array configured as a Raid 5 to another server without losing data? So far I know I'll connect the drive, run devfsadm, use format to verify the server see's... (5 Replies)
Discussion started by: Kjons76
5 Replies

7. UNIX for Advanced & Expert Users

Disk Array

HI: I have a DUAL redundant system running in HP-UX 10.20 ( 2 servers) Both servers share an external SCSI disk array. Both server runs a Data base wich uses the disk array to write the data, and that is the way they share the information. The way that the servers see the disk array, is like... (1 Reply)
Discussion started by: pmoren
1 Replies

8. Filesystems, Disks and Memory

DISK ARRAY PROTECTION SUSPENDED message displayed following disk replacement

Hello, On 4/20/2018, we performed a disk replacement on our IBM 8202 P7 server. After the disk was rebuilt, the SAS Disk Array sissas0 showed a status of degraded. However, the pdisks in the array all show a status of active. We did see a message in errpt. DISK ARRAY PROTECTION SUSPENDED. ... (1 Reply)
Discussion started by: terrya
1 Replies

9. AIX

DISK ARRAY PROTECTION SUSPENDED message following disk replacement

Hello, On 4/20/2018, we performed a disk replacement on our IBM 8202 P7 server. After the disk was rebuilt, the SAS Disk Array sissas0 showed a status of degraded. However, the pdisks in the array all show a status of active. We did see a message in errpt. DISK ARRAY PROTECTION SUSPENDED. ... (3 Replies)
Discussion started by: terrya
3 Replies
xfs_growfs(8)                                                 System Manager's Manual                                                xfs_growfs(8)

NAME
xfs_growfs, xfs_info - expand an XFS filesystem SYNOPSIS
xfs_growfs [ -dilnrxV ] [ -D size ] [ -e rtextsize ] [ -L size ] [ -m maxpct ] [ -t mtab ] [ -R size ] mount-point xfs_info [ -t mtab ] mount-point DESCRIPTION
xfs_growfs expands an existing XFS filesystem (see xfs(5)). The mount-point argument is the pathname of the directory where the filesystem is mounted. The filesystem must be mounted to be grown (see mount(8)). The existing contents of the filesystem are undisturbed, and the added space becomes available for additional file storage. xfs_info is equivalent to invoking xfs_growfs with the -n option (see discussion below). OPTIONS
-d | -D size Specifies that the data section of the filesystem should be grown. If the -D size option is given, the data section is grown to that size, otherwise the data section is grown to the largest size possible with the -d option. The size is expressed in filesystem blocks. -e Allows the real-time extent size to be specified. In mkfs.xfs(8) this is specified with -r extsize=nnnn. -i The new log is an internal log (inside the data section). [NOTE: This option is not implemented] -l | -L size Specifies that the log section of the filesystem should be grown, shrunk, or moved. If the -L size option is given, the log section is changed to be that size, if possible. The size is expressed in filesystem blocks. The size of an internal log must be smaller than the size of an allocation group (this value is printed at mkfs(8) time). If neither -i nor -x is given with -l, the log contin- ues to be internal or external as it was before. [NOTE: These options are not implemented] -m Specify a new value for the maximum percentage of space in the filesystem that can be allocated as inodes. In mkfs.xfs(8) this is specified with -i maxpct=nn. -n Specifies that no change to the filesystem is to be made. The filesystem geometry is printed, and argument checking is performed, but no growth occurs. See output examples below. -r | -R size Specifies that the real-time section of the filesystem should be grown. If the -R size option is given, the real-time section is grown to that size, otherwise the real-time section is grown to the largest size possible with the -r option. The size is expressed in filesystem blocks. The filesystem does not need to have contained a real-time section before the xfs_growfs operation. -t Specifies an alternate mount table file (default is /proc/mounts if it exists, else /etc/mtab). This is used when working with filesystems mounted without writing to /etc/mtab file - refer to mount(8) for further details. -V Prints the version number and exits. The mount-point argument is not required with -V. xfs_growfs is most often used in conjunction with logical volumes (see md(4) and lvm(8) on Linux). However, it can also be used on a regu- lar disk partition, for example if a partition has been enlarged while retaining the same starting block. PRACTICAL USE
Filesystems normally occupy all of the space on the device where they reside. In order to grow a filesystem, it is necessary to provide added space for it to occupy. Therefore there must be at least one spare new disk partition available. Adding the space is often done through the use of a logical volume manager. EXAMPLES
Understanding xfs_info output. Suppose one has the following "xfs_info /dev/sda" output: meta-data=/dev/sda isize=256 agcount=32, agsize=16777184 blks = sectsz=512 attr=2 data = bsize=4096 blocks=536869888, imaxpct=5 = sunit=32 swidth=128 blks naming =version 2 bsize=4096 log =internal bsize=4096 blocks=32768, version=2 = sectsz=512 sunit=32 blks, lazy-count=1 realtime =none extsz=524288 blocks=0, rtextents=0 Here, the data section of the output indicates "bsize=4096", meaning the data block size for this filesystem is 4096 bytes. This section also shows "sunit=32 swidth=128 blks", which means the stripe unit is 32*4096 bytes = 128 kibibytes and the stripe width is 128*4096 bytes = 512 kibibytes. A single stripe of this filesystem therefore consists of four stripe units (128 blocks / 32 blocks per unit). SEE ALSO
mkfs.xfs(8), md(4), lvm(8), mount(8). xfs_growfs(8)
All times are GMT -4. The time now is 09:55 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy