02-27-2006
If you create a large filesystem and then load it with data, the data will be distributed more of less evenly across the entire filesystem. If you extend a filesystem, the free space is mostly at the end of the disk. Either one could be better than the other under various circumstances. Suppose you never add any data...the heads never will need to move to the last 25% (or so) of the disk. Suppose a file near the beginning of the disk grows... it will probably be extended into cylinder groups at the end of the disk. Now the heads must move from one end of the disk to the other end of the disk just to read that file. Because this is Oracle, you need an Oracle expert to comment on this.
But even if you simply extend the filesystem.... (Or even if you leave it at the same size!) you absolutely need a backup! What if you try to extend it and the process fails? If the size of this filesystem is so large that you are having trouble making backups, maybe you should not extend it. Maybe it is time for a new filestem instead. And talk to your DBA. You probably need to use some kind of Oracle backup. You cannot just backup the dbf files of a live database.
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
1 . Thanks everyone who read the post first.
2 . I have a log file which size is 143M , I can not use vi open it .I can not use xedit open it too.
How to view it ?
If I want to view 200-300 ,how can I implement it
3 . Thanks (3 Replies)
Discussion started by: chenhao_no1
3 Replies
2. UNIX for Dummies Questions & Answers
Hi,
I am quite sure that I am posting a question in the very wrong forum but I have to give a try. It's a question about UNIX theory. I don't have any clue of how to solve this question. If someone could kindly provide some good references or give me the formulas, it will be really... (1 Reply)
Discussion started by: ti_ma
1 Replies
3. UNIX for Dummies Questions & Answers
The /src file is obviously designed to contain source code, so when I download programs, I should put them in /src (because they contain the source files + the executables)? What do most people do with the executables? Do they copy them to /bin, make links to them in /bin, or just leave them in... (4 Replies)
Discussion started by: css136
4 Replies
4. UNIX for Dummies Questions & Answers
I have a 5000 line config.log file with several "maybe" errors. Any reccomendations on finding solvable problems? (2 Replies)
Discussion started by: NeedLotsofHelp
2 Replies
5. Shell Programming and Scripting
Input file
DATA2.2 POSITION_152486.2 COLUMN689699.2
DATA2.2 ROW00000342066 UNIT00000342313
DATA7.2 POSITION_017891.4 COLUMN060361.4
DATA7.2 ROW00000379319 UNIT00000368623
DATA7.2 ROW00000421241 UNIT00000400736
DATA8.1 POSITION_153254.2 COLUMN694986.2
DATA8.1 ROW00000379288... (1 Reply)
Discussion started by: perl_beginner
1 Replies
6. UNIX for Dummies Questions & Answers
Does anyone have any idea of how I can make something like the code below run recursively?
I'll run it on a tree of directories all with different names and all containing a sequence of .dpx files. I've tried to do it using find and exec but can't get it to work right.
What it needs to do is... (4 Replies)
Discussion started by: scribling
4 Replies
7. What is on Your Mind?
Hello,
I have been working as Solaris/Linux Admin since past 8 years. I am looking options for my profile change, but there is some limitation. I worked as 24x7 support for admin, server support, high availability, etc. But been worked on developing side and scripting part.
When I search for Big... (2 Replies)
Discussion started by: nightup2222
2 Replies
8. Solaris
Gents
Actually I have question and i need your support.
I have this NAS file system mounted as /coresys has size of 7 TB
I need to Split this file system into several file systems as mount points I mean how to can I Split it professionally to different NAS mount points how to can I decide... (2 Replies)
Discussion started by: AbuAliiiiiiiiii
2 Replies
LEARN ABOUT V7
xfs_freeze
xfs_freeze(8) System Manager's Manual xfs_freeze(8)
NAME
xfs_freeze - suspend access to an XFS filesystem
SYNOPSIS
xfs_freeze -f | -u mount-point
DESCRIPTION
xfs_freeze suspends and resumes access to an XFS filesystem (see xfs(5)).
xfs_freeze halts new access to the filesystem and creates a stable image on disk. xfs_freeze is intended to be used with volume managers
and hardware RAID devices that support the creation of snapshots.
The mount-point argument is the pathname of the directory where the filesystem is mounted. The filesystem must be mounted to be frozen
(see mount(8)).
The -f flag requests the specified XFS filesystem to be frozen from new modifications. When this is selected, all ongoing transactions in
the filesystem are allowed to complete, new write system calls are halted, other calls which modify the filesystem are halted, and all
dirty data, metadata, and log information are written to disk. Any process attempting to write to the frozen filesystem will block waiting
for the filesystem to be unfrozen.
Note that even after freezing, the on-disk filesystem can contain information on files that are still in the process of unlinking. These
files will not be unlinked until the filesystem is unfrozen or a clean mount of the snapshot is complete.
The -u flag is used to un-freeze the filesystem and allow operations to continue. Any filesystem modifications that were blocked by the
freeze are unblocked and allowed to complete.
One of -f or -u must be supplied to xfs_freeze.
NOTES
A copy of a frozen XFS filesystem will usually have the same universally unique identifier (UUID) as the original, and thus may be pre-
vented from being mounted. The XFS nouuid mount option can be used to circumvent this issue.
In Linux kernel version 2.6.29, the interface which XFS uses to freeze and unfreeze was elevated to the VFS, so that this tool can now be
used on many other Linux filesystems.
SEE ALSO
xfs(5), lvm(8), mount(8).
xfs_freeze(8)