Sponsored Content
Top Forums UNIX for Advanced & Expert Users Pros and cons of a Journaled file System Post 302593875 by jlliagre on Sunday 29th of January 2012 05:52:48 PM
Old 01-29-2012
Quote:
Originally Posted by methyl
Main advantage of Journalling Filesystems:
It is possible to configure the computer to survive the common occurrence of single hard disc failure. Most importantly it is possible to configure a system to determine which is the "bad disc".

Main disadvantage of Journalling Filesystems:
Budgetary or irrational design restraints can give a wrong expectation of resilience and cause designers to be complacent about Disaster Recovery backups.
I'm afraid you are confusing journaling file systems and RAID here.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Pro's and cons for Linux

Hi there thanks for checking in The I T manager over here wants us to convert 1 branch in our company from Win98 to Linux I would just like to know the types of problems that we will have once this is done. I would also like to know the following. Does Linux come with a Office package... (3 Replies)
Discussion started by: nemex
3 Replies

2. UNIX for Dummies Questions & Answers

2 simple questions the linux pros will be able to get. Pleese help!

Allright the situation is that i have a dual boot set up with windows xp and red hat 9.0. the problem is that my modem and sound card dont work with linux. I found a driver, and i have to download it with xp. My question is..... How do i actually copy the file to the linux... (4 Replies)
Discussion started by: nregenwether
4 Replies

3. AIX

NFS Pros and Cons

Can anyone provide the pros and cons of having an NFS mount on an AIX server. Or direct me to documentation that provides this information. Thanks... (1 Reply)
Discussion started by: mcateriny
1 Replies

4. AIX

Easy question for you pros

I have a folder with about 4000+ files. I would like to compress all these files with one command. When I type "compress *.ext" for example, I get "arg list too long". I tried the following: for k in * do compress *.ext done Still got "The parameter list is too long." How can I compress... (4 Replies)
Discussion started by: bbbngowc
4 Replies

5. AIX

AIX 5.2/5.3 - rootvg on SAN disk - pros and cons

We are considering a DR strategy of booting AIX 5.3 and 5.3 logical partitions from EMC Symmetrix SAN disks, so that we can replicate via SRDF to a recovery site. Has anyone tried configuring AIX 5.x systems to boot from SAN disk? If so, can you provide any information on the pros and cons of... (6 Replies)
Discussion started by: jjgarrot
6 Replies

6. Cybersecurity

Password Automation pros/cons

folks, I have a security related question, to all you. Please share your comments with me. I have a situation where i was asked to automate the password in my application, which expires every 6 months. In this case i need to generate a random password and set the password on some... (2 Replies)
Discussion started by: sudharma
2 Replies

7. Infrastructure Monitoring

PING pros and cons

I have some questions regarding ping a. im planning to add all my servers to nagios for monitoring purposes. since nagios will do "PING" on the IP address (to check if UP or down), will there be affect on all my servers? say resource utilization, memory, etc? Will it add up or slow down the... (3 Replies)
Discussion started by: lhareigh890
3 Replies

8. Shell Programming and Scripting

Pros and cons for Text User Interface and Curses::UI

Anyone has experience or study with Text User Interface and Curses::UI using Perl? - What is the criteria to decide which method is better for a console based UI? - Which DTL (dialog tag language) is supported by these? The background is that I want to write a wrapper over some UNIX tools... (0 Replies)
Discussion started by: vikrantl
0 Replies

9. Red Hat

Enable journaled quota

Hi guys, I will truly appreciate your help here. How do you enable journaled quota on rhel6? Thank you so much for the assistance. (2 Replies)
Discussion started by: cjashu
2 Replies
BBSTOREACCOUNTS(8)						    Box Backup							BBSTOREACCOUNTS(8)

NAME
bbstoreaccounts - Box Backup store accounts manager SYNOPSIS
bbstoreaccounts [-c config-file] command account-id [command-specific arguments] DESCRIPTION
bbstoreaccounts is the tool for managing accounts on the store server. It can be used to view information related to accounts, as well as create, change and delete accounts on the store server. bbstoreaccounts always takes at least 2 parameters: the command name and the account ID. Some commands require additional parameters, and some commands have optional parameters. Options -c config-file The configfile to use for connecting to the store. Default is /etc/box/bbstored.conf. Commands The commands tells bbstoreaccounts what action to perform. check account-id [fix] The check command verifies the integrity of the store account given, and optionally fixes any corruptions. Note: It is recommended to run the 'simple' check command (without fix) before using the fix option. This gives an overview of the extent of any problems, before attempting to fix them. create account-id disc-set soft-limit hard-limit Creates a new store account with the parameters given. The parameters are as follows: account-id The ID of the new account to be created. A 32-bit hexadecimal number. Cannot already exist on the server. disc-set The disc set from raidfile.conf(5) where the backups for this client will be stored. A number. Each RAID-file set has a number in raidfile.conf. This number is what's used. soft-limit The soft limit is the amount of storage that the server will guarantee to be available for storage. hard-limit The amount of storage that the the server will allow, before rejecting uploads, and starting to eliminate old and deleted files to get back down to soft-limit. delete account-id [yes] Deletes the account from the store server completely. Removes all backups and deletes all references to the account in the config files. delete will ask for confirmation from the user, when called. Using the yes flag, eliminates that need. This is useful when deleting accounts from within a script or some other automated means. 0 info account-id Display information about the given account. Example: [root]# bbstoreaccounts info 1 Account ID: 00000001 Last object ID: 58757 Blocks used: 9864063 (38531.50Mb) Blocks used by old files: 62058 (242.41Mb) Blocks used by deleted files: 34025 (132.91Mb) Blocks used by directories: 6679 (26.09Mb) Block soft limit: 11796480 (46080.00Mb) Block hard limit: 13107200 (51200.00Mb) Client store marker: 1139559852000000 Explanation: Account ID The account ID being displayed. Last Object ID A counter that keeps track of the objects that have been backed up. This number refers to the last file that was written to the store. The ID is displayed as a decimal number, and the object ID can be converted to a path name to a file as follows: convert the number to hex (e.g.: 58757 => 0xE585); The last backed up file will be (relative from the client's store root): e5/o85.rfw. Longer numbers infer more directories in the structure, so as an example 3952697264 as the last object ID gives 0xEB995FB0, which translates to a backup pathname of eb/99/5f/ob0.rfw. Blocks used The number of blocks used by the store. The size in Mb depends on the number of blocks, as well as the block size for the disc set given in raidfile.conf(5). In this case the block size is 4096. Blocks used by old files The number of blocks occupied by files that have newer versions in the store. This data is at risk for being removed during housekeeping. Blocks used by deleted files The number of blocks used by files that have been deleted on the client. This data is at risk for being removed during housekeeping. Blocks used by directories The number of blocks used by directories in the store. Block soft limit The soft limit in blocks. The soft limit is the maximum guaranteed storage space available to the account. When housekeeping starts, and the old and deleted files are removed, they are removed in chronological order (oldest first), until the data used is less than the soft limit. Block hard limit The hard limit in blocks. The hard limit is the most amount of storage the server will allow in an account. Any data above this amount will be rejected. Housekeeping will reduce the storage use, so more data can be uploaded. Client store marker bbstored(8) uses this number to determine if it needs to rescan the entire store. If this number is different from the last time it checked, a rescan will take place. setlimit account-id soft-limit hard-limit Changes the storage space allocation for the given account. No server restart is needed. Parameters: account-id The ID of the account to be modified. soft-limit The soft limit is the amount of storage that the server will guarantee to be available for storage. hard-limit The amount of storage that the the server will allow before rejecting uploads and starting to eliminate old and deleted files to get back down to soft-limit. EXAMPLES
Create an account with ID 3af on disc set 0, with a 20GB soft-limit and a 22GB hard-limit: bbstoreaccounts create 3af 0 20G 22G Alter existing account ID 20 to have a 50GB soft-limit and a 55GB hard-limit: bbstoreaccounts setlimit 20 50G 55G FILES
/etc/box/bbstored/accounts.txt SEE ALSO
bbstored(8), bbstored-config(8) AUTHORS
Ben Summers Per Thomsen James O'Gorman Box Backup 0.11 10/28/2011 BBSTOREACCOUNTS(8)
All times are GMT -4. The time now is 11:52 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy