If it is the same file -
Versions 4.0 and higher handoff regions of a file to different hosts to
reduce lock contention. Depends on the file size and whether the hosts
are accessing the same region of the file as to whether this would help
(also depends what version you're running - if 4, you've
also use fsadm to change the log size. From the
manpage
-o specific_options
Specifies VxFS-specific options.
largefiles
Sets the largefiles flag for the file
system. When this flag is set, large
files (greater than two gigabytes) can
be created on the
You can also grow the log using fsadm, if you don't want to place it on
a separate device and it was built too small originally. Man fsadm_vxfs
for the specific flag.
Regards,
Scott
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Par Botes
Sent:
It may also depend on the version. What version are you running?
Regards,
Scott
_
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Nath
Pankaj-a22823
Sent: Monday, March 05, 2007 10:57 PM
To: veritas-vx@mailman.eng.auburn.edu
Subject:
Leon,
What VxFS version and block size and disklayout do you have?
For multi-TB file systems, you generally need some combination of:
Larger block sizes
Newer Binaries
Newer disklayouts
Regards,
Scott
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
This is not going to be an official or comprehensive post, so caveat
reador...
In addition to VRTSvxvm, vxfs, and vlic, there are a number of other
packages that are not GUI nor SFMS related, but you may find useful. I
don't have a comprehensive list, but here are some examples (skipping
the VRTS
Max file system sizes on Solaris:
3.0.2 - almost certainly 1TB
3.5 - 32TB
4.x - 256TB
The 3.5 and 4.x size limits assume an 8k block size. For each block size
smaller (4k, 2k, 1k) knock down the max file system size by a power of
2. You'll need to be on the highest disklayout version to get the
Also, if your mirror is 'semi-local' - in another building, or even
several miles away, _and_ you have FC run between the two locations, you
can set up a stretch cluster via VxVM mirroring.
Regards,
Scott
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Also note that if using CFS 5.0 disklayout 7 (the default for a new
file system), selecting the CFS primary is essentially irrelevent, as
all cluster nodes participate in metadata transactions. The CLI to
select is kept primarily for backward compatability.
Scott
-Original Message-
Some of that reported unusable is actually usable.
VxFS doesn't make many inodes in advance, it allocates creates them
as-needed.
UFS, by contrast, creates inodes at a fixed ratio to storage, and the
space those inodes consume truly is unusable.
But, if VxFS reports that space as free, then as
Yes, you need to be on version 4.1 or 5.0 of VxVM for Solaris 10
support.
From a license perspective, as long as you have current maintenance
contract for that box, you are entitled to an upgrade.
Scott
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Couple of comments
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Svoboda, Michael Steven
Sent: Wednesday, September 05, 2007 9:03 AM
To: veritas-vx@mailman.eng.auburn.edu
Subject: [Veritas-vx] does fsadm defragmentation require
additional
1000 isn't a particularly large number of LUNs, even for 4.1 (although
5.0 will handle such configurations much better and faster). Can you
open a support case for this?
Regards,
Scott
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of ashish
I understand that Veritas provides supporting utilities for use with
LU, I haven't used them personally.
I haven't seen that.
the commands are:
vxlustart
vxlufinish
Regards,
Scott
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of A Darren
Dunham
Two options:
1. use a command from the database edition that provides this sort of
mapping:
vxstorage_stats
Although this command was targeted at the database market, it works on
any file.
The requirements and such are in chapter ~8 of the DBED Administrator's
Guide. Man page below. Note that,
Is this the same operating system or different?
The LUNs need to be visible from the other server (could be a physical
connectivity or zoning issue, or if you have an older OS they sometimes
need some 'prodding'), and the mount points should be created via mkdir
before you migrate (no sense in
In theory you can check it here:
http://www.symantec.com/business/support/release_details.jsp?pid=15107
just pull down the version and platform.
However, when I do that for Solaris 4.1, the answer seems to be somewhat
misleading. Full support for sev 34 on 4.1 Solaris SPARC ended December
Inodes are dynamically allocated in VxFS, so that's not likely to be the cause
(unless you have a multiple billion inodes or a very, very old disk layout).
Enhancements were a couple versions ago to reserve space internally within the
file system so users wouldn't have to manually reserve free
There were no ASLs in VxVM 3.2. ASLs weren't introduced until VxVM 4.0,
two releases later.
Regards,
Scott
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Paul
Liong
Sent: Monday, April 28, 2008 6:44 PM
To: veritas-vx@mailman.eng.auburn.edu
Subject:
Here was some response from a developer
If you do not have volumes/FS ready, you can re-run sfua_db_config later
after you create volume/FS.
Regards,
Scott
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Prasad Chalikonda
Sent: Thursday, May 08,
Also NetBackup.
Regards,
Scott
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Thursday, May 15, 2008 3:19 AM
To: veritas-vx@mailman.eng.auburn.edu
Subject: [Veritas-vx] storage checkpoint - recommended ways to dump to
tape
Hi,
Here is a suggestion --
--
Apparently DBAs access to /opt/VRTSdbed was at installation time.
See the snippet from the Installation Guide below.
--
Setting Administrative Permissions
The VxDBA utility
Three other points --
1. Checkpoints use the free space within the file system. Snapshots need
a dedicated, separate disk/LUN
2. Checkpoints have several optimized code paths, so their overhead is
lower than that of Snapshots.
3. Snapshots provide a raw device view of the file system (checkpoints
In addition to snapshot, errno 16 can be caused if the fullfsck flag is
set.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Luke
Francis, Aju
Sent: Monday, August 11, 2008 4:55 AM
To: Praveent T M; veritas-vx@mailman.eng.auburn.edu
Subject: Re:
Hi Mike,
Interesting question, I had to check with development. Here's the info:
#define VX_SINGLEDEV0x4000 /* only one dev for fs */
In 4.0, vxfs allows for more than one volume (device, hence dev) in a
single file system.
In disklayout 7, a flag was added to signify that a file
Hi Przemyslaw,
Have you looked at the existing quotas?
http://sfdoccentral.symantec.com/sf/5.0/solaris/manpages/vxfs/fsckptadm_
1m.html#429951
The -r option doesn't delete any checkpoints, it just makes each
individual checkpoint 'removable'. Plus, it's been the default since
4.0, so unless you
4.x keys will work with 5.0 binaries.
5.0 keys will not, as a rule, work with 4.x binaries.
Scott
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bonfoey,
Richard
Sent: Friday, October 03, 2008 10:29 AM
To: veritas-vx@mailman.eng.auburn.edu
Andrey,
After speaking to a couple of developers, they think this is likely
fixed by etrack 1416931 (sun id 6747492) which has been fixed and
checked in.
Regards,
Scott
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Andrey
Dmitriev
Sent: Thursday,
28 matches
Mail list logo
