08-25-2009
Quote:
Originally Posted by
mark54g
Also, please tell me that your "backups" are also going to another spot other than just a RAID 5 set.
Yes, 32-64K would be good for non sequential (sequential would be something like linear video or audio files). 128K would possibly be ideal if your files are greater than 8MB on average.
However, as others have stated, RAID 0, while improving performance, will actually increase the likelihood of failure from even having 1 drive.
yup my "backups" are going into a external 1.5TB... I dont think the OS files are larger than 8MB.. So i guess 32k would be ideal?? i can go as low as 4k
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi all
I am working on MSR110 ...Can anyone plz tell me how to use the configuration commands with magnetic reader???. Please help me out as i have to develop API in C on linux platform.MSR110 is not responding to the configuration commands.
Please help...
Regards
Mahima (0 Replies)
Discussion started by: mahima_er
0 Replies
2. UNIX for Advanced & Expert Users
Hi,
Is there are any special preocedure for extending veritas mirror-stripe volume? In my case , volume lay out looks as below
v test - ENABLED ACTIVE 419430400 SELECT - fsgen
pl test-01 test ENABLED ACTIVE 419454720 STRIPE 3/128 RW
sd... (0 Replies)
Discussion started by: 2k7.vipin
0 Replies
3. AIX
Hello all.
I have a volume group with 8 PV's, and a logical volume striped across these 8 volumes.
However, an lslv is showing:
STRIPE WIDTH: 9
STRIPE SIZE: 64k
There's really only eight disks, so how can the stripe width be 9?
ODM also showed this:
# odmget CuAt |... (4 Replies)
Discussion started by: Scott
4 Replies
4. Emergency UNIX and Linux Support
Hi all
I have just had SAN allocate 4*30 GB of disks and had created a new scalable vg and assigned the disks to it:
I used smitty to create vg and the command is: x -y'vgdata1' hdisk82 hdisk83 hdisk84 hdisk85
root@aadcxs08 / : lsvg vgdata1
VOLUME GROUP: vgdata1 VG... (4 Replies)
Discussion started by: hedkandi
4 Replies
5. AIX
Hello,
I have a scsi pci x raid controller card on which I had created a disk array of 3 disks
when I type lspv ; I used to see 3 physical disks ( two local disks and one raid 5 disk )
suddenly the raid 5 disk array disappeared ; so the hardware engineer thought the problem was with SCSI... (0 Replies)
Discussion started by: filosophizer
0 Replies
6. Solaris
Server Model: T5120 with 146G x4 disks.
OS: Solaris 10 - installed on c1t0d0.
Plan to use software raid (veritas volume mgr) on c1t2d0 disk.
After format and label the disk, still not able to detect using vxdiskadm.
Question:
Should I remove the hardware raid on c1t2d0 first?
My... (4 Replies)
Discussion started by: KhawHL
4 Replies
7. Solaris
Hello Admins..
I am going through solaris volume manager guide for RAID-0 concatenation and stripes, I do not understand the concept of stripe from following example of concatenation.
There is an eample for concatenation:
# metainit d25 1 1 c0t1d0s2
d25: Concat/Stripe is setup
the... (5 Replies)
Discussion started by: snchaudhari2
5 Replies
8. Red Hat
Hello,
I want to delete a RAID configuration an old server has.
Since i haven't the chance to work with the specific raid controller in the past can you please help me how to perform the configuraiton?
I downloaded IBM ServeRAID Support CD but i wasn't able to configure the video card so i... (0 Replies)
Discussion started by: @dagio
0 Replies
9. Shell Programming and Scripting
Say i have:
g_gateway domain="abc.com" to="123.123.123.123" relay="false"
how do i use awk or sed or any method to get the result below:
abc.com 123.123.123.123 (3 Replies)
Discussion started by: timmywong
3 Replies
LEARN ABOUT DEBIAN
s3qllock
S3QLLOCK(1) S3QL S3QLLOCK(1)
NAME
s3qllock - Make trees on an S3QL file system immutable
SYNOPSIS
s3qllock [options] <directory>
DESCRIPTION
S3QL is a file system for online data storage. Before using S3QL, make sure to consult the full documentation (rather than just the man
pages which only briefly document the available userspace commands).
The s3qllock command makes a directory tree in an S3QL file system immutable. Immutable trees can no longer be changed in any way whatso-
ever. You can not add new files or directories and you can not change or delete existing files and directories. The only way to get rid of
an immutable tree is to use the s3qlrm command.
s3qllock can only be called by the user that mounted the file system and (if the file system was mounted with --allow-other or
--allow-root) the root user. This limitation might be removed in the future (see issue 155).
RATIONALE
Immutability is a feature designed for backups. Traditionally, backups have been made on external tape drives. Once a backup was made, the
tape drive was removed and locked somewhere in a shelf. This has the great advantage that the contents of the backup are now permanently
fixed. Nothing (short of physical destruction) can change or delete files in the backup.
In contrast, when backing up into an online storage system like S3QL, all backups are available every time the file system is mounted.
Nothing prevents a file in an old backup from being changed again later on. In the worst case, this may make your entire backup system
worthless. Imagine that your system gets infected by a nasty virus that simply deletes all files it can find -- if the virus is active
while the backup file system is mounted, the virus will destroy all your old backups as well!
Even if the possibility of a malicious virus or trojan horse is excluded, being able to change a backup after it has been made is generally
not a good idea. A common S3QL use case is to keep the file system mounted at all times and periodically create backups with rsync -a. This
allows every user to recover her files from a backup without having to call the system administrator. However, this also allows every user
to accidentally change or delete files in one of the old backups.
Making a backup immutable protects you against all these problems. Unless you happen to run into a virus that was specifically programmed
to attack S3QL file systems, backups can be neither deleted nor changed after they have been made immutable.
OPTIONS
The s3qllock command accepts the following options:
--debug
activate debugging output
--quiet
be really quiet
--version
just print program version and exit
EXIT STATUS
s3qllock returns exit code 0 if the operation succeeded and 1 if some error occurred.
SEE ALSO
The S3QL homepage is at http://code.google.com/p/s3ql/.
The full S3QL documentation should also be installed somewhere on your system, common locations are /usr/share/doc/s3ql or
/usr/local/doc/s3ql.
COPYRIGHT
2008-2011, Nikolaus Rath
1.11.1 August 27, 2014 S3QLLOCK(1)