01-11-2008
RAID5 problems on solaris
I have one volume raid5 with 3 slice one of them is maintenance state. I replace this slice and resync the volume. when I try to mount the file system another slice goes to last erred. Again resync and the state goes to OK but the slice in mantenance persist. I try to enabled this but persist in manitenance state.
What can I do , I have a lot of critical data here without backup of this
Thanks
Daniel
10 More Discussions You Might Find Interesting
1. SCO
Forgive me, I do not know much about RAID so I'm going to be
as detailed as possible.
This morning, our server's alarm was going. I found that one
of our drives have failed. (we have 3)
It is an Adaptec ATA RAID 2400A controller
I'm purchasing a new SCSI drive today. My questions:
... (2 Replies)
Discussion started by: gseyforth
2 Replies
2. AIX
hi all,
i have an p620 server. it has 2 scsi 18gb disks for aix4.3 OS and 3 ssa disks for database and an serialRAID adapter. 3 ssa disks configured raid level 5.
to increase capacity of the datavg, i buy 2 ssa 18gb disks. but i can not add them to the existing datavg. i did the following... (1 Reply)
Discussion started by: tinhlx
1 Replies
3. AIX
Hello All.
Is it possible? (5 Replies)
Discussion started by: sapbcer
5 Replies
4. AIX
Hi,
I have an ssa filesystem to move to san. We don't want any downtime. I heard that you can do a mirroring of existing file system on the san. The file system is a type of either raid 0, raid 1, or raid 5.
Anyone know how to do this?
Thanks in advance,
itik (4 Replies)
Discussion started by: itik
4 Replies
5. Filesystems, Disks and Memory
Hello, we have a problem with our system, a machine with a RAID5:
- We can boot the system from CD only, if we try to boot from hard-disk the GRUB seems to be "freezed". What is the difference, why we can boot from CD if something is wrong?
- Allways we retreive an error like: "raid array is... (6 Replies)
Discussion started by: aristegui
6 Replies
6. Red Hat
is placing two RAID5 arrays on disk as shown below Is advisable? Will this create performance problems?
sda-(500GB) sdb-(1TB) sdc-(1TB) sdd-(1TB)
(250MB)----------(250MB) ---------unused------------unused------->(/dev/md0) RAID1
... (6 Replies)
Discussion started by: Saed
6 Replies
7. UNIX for Advanced & Expert Users
Hi there,
Don't know if my title is relevant but I'm dealing with dangerous materials that I don't really know and I'm very afraid to mess anything up.
I have a Debian 5.0.4 server with 4 x 1TB hard drives.
I have the following mdstat
Personalities :
md1 : active raid1 sda1 sdd1... (3 Replies)
Discussion started by: chebarbudo
3 Replies
8. SuSE
Hi all,
I am currently using opensuse 12.1,
We have Raid 5 array of 8 disks. A friend of mine accidently removed a drive & place it back and also added a new disk to it(making it 9 disks). now the output of mdadm --detail is as shown below
si64:/dev # mdadm --detail /dev/md3
/dev/md3:... (1 Reply)
Discussion started by: patilrajashekar
1 Replies
9. Hardware
Hello Experts,
I have few doubts on RAID 5 with LUNs carved as STRIPE and CONCAT
RAID 5 = STRIPE + Parity mirroring
I would like to know if the LUNs carved are CONCATE from RAID 5 disk array. Are the I/Os are spread accross the disks within the RAID 5 Array? And if I do carve STRIPED... (1 Reply)
Discussion started by: sybadm
1 Replies
10. Red Hat
Hi All,
I have a new x3650 M4 server with hardware RAID 5 configured 4 x 300 GB (HDD).
The Raid controller is ServeRAID M5110e.
Im getting "device not found" error during hardisk detection of RHEL6 install using DVD.
Some pages over the net pointed to using ServerGuide media for... (1 Reply)
Discussion started by: Solaris_Begin
1 Replies
LEARN ABOUT ULTRIX
systemd.slice
SYSTEMD.SLICE(5) systemd.slice SYSTEMD.SLICE(5)
NAME
systemd.slice - Slice unit configuration
SYNOPSIS
slice.slice
DESCRIPTION
A unit configuration file whose name ends in ".slice" encodes information about a slice unit. A slice unit is a concept for hierarchically
managing resources of a group of processes. This management is performed by creating a node in the Linux Control Group (cgroup) tree. Units
that manage processes (primarily scope and service units) may be assigned to a specific slice. For each slice, certain resource limits may
be set that apply to all processes of all units contained in that slice. Slices are organized hierarchically in a tree. The name of the
slice encodes the location in the tree. The name consists of a dash-separated series of names, which describes the path to the slice from
the root slice. The root slice is named -.slice. Example: foo-bar.slice is a slice that is located within foo.slice, which in turn is
located in the root slice -.slice.
Note that slice units cannot be templated, nor is possible to add multiple names to a slice unit by creating additional symlinks to its
unit file.
By default, service and scope units are placed in system.slice, virtual machines and containers registered with systemd-machined(1) are
found in machine.slice, and user sessions handled by systemd-logind(1) in user.slice. See systemd.special(5) for more information.
See systemd.unit(5) for the common options of all unit configuration files. The common configuration items are configured in the generic
[Unit] and [Install] sections. The slice specific configuration options are configured in the [Slice] section. Currently, only generic
resource control settings as described in systemd.resource-control(5) are allowed.
See the New Control Group Interfaces[1] for an introduction on how to make use of slice units from programs.
IMPLICIT DEPENDENCIES
The following dependencies are implicitly added:
o Slice units automatically gain dependencies of type After= and Requires= on their immediate parent slice unit.
DEFAULT DEPENDENCIES
The following dependencies are added unless DefaultDependencies=no is set:
o Slice units will automatically have dependencies of type Conflicts= and Before= on shutdown.target. These ensure that slice units are
removed prior to system shutdown. Only slice units involved with late system shutdown should disable DefaultDependencies= option.
SEE ALSO
systemd(1), systemd.unit(5), systemd.resource-control(5), systemd.service(5), systemd.scope(5), systemd.special(7), systemd.directives(7)
NOTES
1. New Control Group Interfaces
https://www.freedesktop.org/wiki/Software/systemd/ControlGroupInterface/
systemd 237 SYSTEMD.SLICE(5)