It feels like everyone is very much looking forward for this neat device. Although the device is getting tons of positive buzz, there will always be some flaws on that ‘perfect product’.

Check out this spoof video, an ipad parody of the missing features of the IpAd such as a built-in camera, printing support, voice and others.

Funny.

getfacl is a file utility for viewing the access control list information associated with a file or directory.

For a memory aid, you can think of ‘getfacl’ as “Get File ACL“.. ACL being Access Control List.

Access control lists are extended attributes added to most major file systems in the 2.6 kernel to improve ability to control the access of files. They allow permissions to be set for individual groups and users and not just the owning user, owning group, and all other users.

setfacl is a command that allows you to set the Access Control List information for a file or directory.

Access control lists are extended attributes added to most major file systems in the 2.6 kernel to improve ability to control the access of files. They allow permissions to be set for individual groups and users and not just the owning user, owning group, and all other users.

You can read man pages for both getfacl and setfacl for more information.

getfacl and setfacl example….

Here’s an example of using the basic funtion of getfacl and setfacl

# getfacl

#setfacl

setfacl -m default:user::rwx,default:group::r-x,default:other:r-x,default:mask:rwx /u06/OneSource/datapump_dbdump

setfacl -m default:user:rcodapp1:r-x,default:group:r-x,default:other:—,default:mas:rwx /u06/OneSouce/datapump_dbdump

And here are the cheat sheet for ZFS/zpool that is related to this week’s project.

The whole exaple uses virtual devices.. that is chucks of files that represents disk.. of course if you have physical disk available, you may use those.

Here’s how to create “virtual devices” or vdevs as described in the zpool documentation. These can also be real disk slices if you have them available.

$ su
Password:
# cd /
# mkfile 100m disk1 disk2 disk3 disk5
# mkfile 50m disk4
# ls -l disk*
-rw------T 1 root root 104857600 Sep 11 12:15 disk1
-rw------T 1 root root 104857600 Sep 11 12:15 disk2
-rw------T 1 root root 104857600 Sep 11 12:15 disk3
-rw------T 1 root root 52428800 Sep 11 12:15 disk4
-rw------T 1 root root 104857600 Sep 11 12:15 disk5


Here’s how to create a storage pool and check the size and usage.

# zpool create myzfs /disk1 /disk2
# zpool list
NAME SIZE USED AVAIL CAP HEALTH ALTROOT
myzfs 191M 94K 191M 0% ONLINE -

When you created a disk pool, you can create a ZFS Filesystem which also in turn,

Create a second file system. Note that both file system show 159M available because no quotas are set. Each “could” grow to fill the pool.

# zfs create myzfs/colin2
# zfs list
NAME USED AVAIL REFER MOUNTPOINT
myzfs 172K 159M 21K /myzfs
myzfs/colin 18K 159M 18K /myzfs/colin
myzfs/colin2 18K 159M 18K /myzfs/colin2

Reserve a specified amount of space for a file system ensuring that other users don’t take up all the space.

# zfs set reservation=20m myzfs/colin
# zfs list -o reservation
RESERV
none
20M
none

Set and view quotas

# zfs set quota=20m myzfs/colin2
# zfs list -o quota myzfs/colin myzfs/colin2
QUOTA
none
20M

Destroy a filesystem

# zfs destroy myzfs/colin2
# zfs list
NAME USED AVAIL REFER MOUNTPOINT
myzfs 20.1M 139M 22K /myzfs
myzfs/colin 18K 159M 18K /myzfs/colin
myzfs/colin@test 0 – 18K -
myzfs/colin3 0 139M 18K /myzfs/colin3

That’s what I need for now.. will continue addiction ZFS cheat sheet if needed.. Pardon me, but my primary use of this blog site is for my use

Once a survey has been created, data can be inserted into the survey either by a “pretty” public screen which presents each question one at a time, or by a quick and nasty data entry screen. It includes the capacity to generate individualized “tokens”, so that invitation can be issued to participants. It also has the capacity to set conditions on whether questions will display (branching), numerous question types, and a basic statistics function. Changes: A Malay translation was added, several minor bugs were fixed, and translations were updated.

There’s this 2 new Wordpress plugin here in Sysadmindayph dot com (the newest that I installed at least). I just want to share this one for the readers of this blog who is also Wordpress user.

The two new plugins here are:

• SEO Smart Link
• Broken Link Checker

SEO Smart Link – SEO Smart Links can automatically link keywords and phrases in your posts and comments with corresponding posts, pages, categories and tags on your blog.

Broken Link Checker – This plugin will monitor your blog looking for broken links and let you know if any are found.

I want to post… say, borrowing, the content of that page to this post for my own personal reference… Love your own page right? And since I am more likely to open SysadminPH that cuddletech, I thought we not copy the Veritas tutorial page here for my ease of access?

The Cuddletech Veritas Cheat Sheet

by: B. Rockwood
benr@cuddletech.com

Overview:
——–

The purpose of this paper is to
quickly get you up to speed in Veritas,
and to act as a quick referance. All new
users to Veritas are HIGHLY encouraged to
first read the Veritas users guides enlucded
with Veritas, and found on docs.sun.com

Remember!: Almost all commands can use several
diffrent options that are similar
across all commands. The most used
of these is “-g ” which
specifies which Disk Group the command
will be executed on. For instance,
vxinfo will only display volume information
for volumes in the rootdg, to see
volumes in the datadg, for instance, use:
Ex: “vxinfo -g datadg”

———————————————–
DISPLAY and MONITORING
———————————————–

vxdisk list
List all disks used by Veritas (VX).

vxdisk list
Display detailed information about a
single disk, including mutlipathing
information, size, type, Vx version,
and more.

vxprint
Display report style information about
the current status of all Vx componants,
including disks, subdisks, plexes, and
volumes.

vxprint
Display report style information about
the current status of ONLY the componant
you request. So for instance,
“vxprint vol01″ shows information about
all subcomponants of vol01. This works
for plexes, disk groups, etc.

vxprint -hrt
Display detailed information about all
Vx componanats, including stwdith,
ncolumns, offsets, layout type, read-
policy, and more. This is best for
a true picture of your configuration.

vxdg list
Display listing and state information
of all Disk Groups.

vxdg list
Display detailed information about
a diskgroup, including flags, version,
logs status, etc.

vxinfo
Display volume status and volume type.
By default, only displays “rootdg”,
to display a diffrent Disk Group,
use “vxinfo -g “.

vxassist maxgrow
This command will output the maximum size
the volume specified can increased by,
specified in sectors.

————————————————–
DISK TASKS and COMMANDS
————————————————–

vxdiskadd
Adds a disk to Vx by Initializing and Encapsolating
it. Specified by its device name (ex: c0t1d0s2).
NOTE: You’ll need to reboot to finalize the
disk addition!

This command, can also be used to add a disk to
a specified disk group. Just follow the prompts.
No reboots needed for changing DG’s.

vxedit rename
Rename a Vx disk. Ex: “vxedit rename disk01 disk05″

vxedit set reserve=on
Sets the “reserve” flag to a Vx disk. This
is used to keep specific disks from being
accidentally, or generally used.

vxdisk offline
Used to “offline” a disk. The disk should
be removed from its diskgroup before being
offlined.

vxdisk rm
Used to remove disks from Vx control completely.
Ex: “vxdisk rm c0t1d0s2″ Make sure to
removed the disk from its diskgroup, and offline
the disk before removing it.

vxedit set spare=on
Sets the “spare” flag to a Vx disk. This is used
to make the specified disk a hot spare, which
is then added to the “hot spare pool”.

vxedit set spare=off
Same as above but removes the disk from the
“hot spare pool”.

—————————————————-
DISK GROUPS and COMMANDS
—————————————————-

vxdg init =
Creates a new disk group, and assigns the naming
scheme to the first disk added to the group.
ex: “vxdg init newdg newdg01=c0t10d0s2″.
NOTE: This is kinda tricky because the disk that
you’re adding can’t be a member of ANY DG, but
must be initialized. It’s easier to use
“vxdiskadd”, and add the disk to a newdg by
specifying a new DG name for the DG field.

vxdg deport
Disabled a diskgroup, but doesn’t remove it. Often
used as an organized pool of disk to realocate, and
to moved DG’s from one system to another.

vxdg import
Reverse of above. Enables local access to the specified
disk group.

vxdg -n Change a Disk Groups name.

vxdg list
Use this to check the version numbers of Disk
Groups. Shows other details about the DG too.

vxdg destroy
Removes the specified DG, and frees all its disks
back to general use by Vx.

-= Quick Chart!: Disk Group Version Number Translation

VxVM Introduced Supported
Release Version Versions
——- ———— ———
1.2 10 10
1.3 15 15
2.0 20 20
2.2 30 30
2.3 40 40
2.5 50 50
3.0 60 20-60

———————————————————–
SUBDISKS and COMMANDS
———————————————————–

vxmake sd ,,
Creates a subdisk with the specified name,
and by the offset and length specified.
ex: “vxmake sd disk02-01 disk02,0,8000″
NOTE: If you are going to add this subdisk
to a plex, its good to check the other
subdisks in that plex to see what their
lengths and offsets are, use the command:
“vxprint -st”

vxedit rm
Removes a subdisk.

vxsd assoc ,….
Associates the specified subdisks to
the specified plex. Example:
“vxsd assoc vol01-03 disk01-01,disk02-01″
NOTE: Striped volumes are diffrent,
you need to specify the column# so
use the following:

vxsd -l
assoc ,…
Same as above, but used for associating
subdisks to a striped plex. Use the command
“vxprint -st” to see what other subdisk
in the plex look like, and then set the
new subdisks column number and offset
(found in the seventh column of output)
to the appropriate value.

vxsd aslog
Adds a log subdisk to the specified plex.
Ex: “vxsd aslog vol01-02 disk03-01″

vxsd dis
Disassociates the specified subdisk from its
current plex.

——————————————————
PLEXS and COMMANDS
——————————————————

vxmake plex sd=,,….
Creates a new plex by the name specified and
assigns the specified subdisks to it.

vxmake plex layout= stwidth= ncolumn= sd=…
Like above command, but specifies layout type
as defined by , which is used for creation
of striped and RAID5 plexes. The layout is
constrained by the defined number of columns,
and stripe width. Subdisks specified are
added to the created plex.

vxplex att Associates specified plex with specified volume.
(Adds a mirror)
NOTE: Attachment will take a while. Watch
it with Vxtask, or via vxprint

vxplex dis Disassociate specified plex from its connected
volume.

vxedit -r rm Remove the plex.

vxmend off Offlines a plex for repair to it’s disks.

vxplex det Detaches specified plex from its connected
volume, but maintians association with it’s
volume. The plex is no longer used
for I/O untill it is (re)attached.

vxmend fix clean Used to clean plexes that are in the
“unclean” state. Used with unstartable
volumes.

vxplex mv
Moves the data content from the origonal
plex onto a new plex.
NOTE: The old plex must be active (ENABLED).
The new plex should be the same length, or
larger than the old plex. The new plex
must not be associated with another volume.
(duh)

vxplex cp
Copies the data from the specified volume
to a new plex.
NOTE: The new plex cannot be associated
with any other volume. The new plex,
further, will NOT be attached to
the specified volume. (Also, see notes
from above)

——————————————————-
VOLUMES and COMMANDS
——————————————————-

vxassist make
Creates a new volume with the name specified
and is made to the length specified.
Ex: “vxassist make newvol 10m”
NOTE: This command will pull disk space
from the generally avalible Vx disk space.

vxassist make layout= ….
Like the above command, but with layout specified.
The most common layouts are: striped and raid5
ex: “vxassist make newvol 100m layout=raid5 disk01 disk02 disk03″
NOTE: See the vxassist(1M) man page for more information.

vxmake vol len= plex= ,…
Creates a new volume of specified length (usually
in sectors), and attachs the specified plexes to that
volume. Useful for creating volumes to house
copied or moved plexes.
NOTE: See the vxmake(1M) man page for more information.

vxvol init [plexname]
Manually sets the state of a volume.
NOTE: Not for the squimish.

vxassist maxsize [layout=raid5]
Returns the maximum size avalible via Vx to create
a new volume. By adding “layout=raid5″ to the command
the calulations take into account losse due
to raid5. Output is in sectors and Megs.

vxassist maxgrow
Returns the maximum ammount of Vx space that
can be added to the specified volume.

vxassist mirror
Creates a mirror for the specified volume.
NOTE: Think of this as “handsfree plex creation”.
This is fast, but the disks you want used
may not be used… often best to do manually.

vxassist addlog
Adds a Dirty Region Log (DRL) for the specified volume.

vxassist remove log
Reverse of above.

vxvol start
Starts a volume

vxvol stop
Stops a volume. Alternately you can use command as
such: “vxvol stopall” in order to stop all volumes.

vxassit growto/growby/shrinkto/shrinkby
Resizes the volume specified. Use one of the
following: growto, growby, shrinkto, and shrinkby
in order to descide what specifies.
By default length is specified in sectors.
This does not resize the filesystem inside the volume.
NOTE: Don’t shrink volumes to be less that
its contained filesystem! (duh)

vxvol set len=
An alternate to above command. Sets the absolute
lenths of the specified volume to the length
specified, by default, in sectors. This
does not resize the filesystem inside the volume.

NOTE: There is also a resize(1M) command, used
for resizing both volume AND filesytem. See
the man page for that one.

vxedit rm
Removes the specified volume. (poof!)
NOTE: If the volume specified is in the ENABLED
state, you will need to use the command
“vxedit -f “. Also, using the “r”
with “f” will remove all plexes and subdisks
with the volume. If you didn’t guess, “r”
is Recursive, and “f” is Force.

—————————————————————-
Misc Stuff:

To calculate the size of a filesystem inside a volume, use
the command:
fstyp -v | head -30 | grep ncg
Ignore the errors. Output will look this this:
# fstyp -v /dev/vx/rdsk/datadg/vol01 | head -30 | grep ncg
ncg 17152 size 70254592 blocks 65863396
# Broken Pipe
Unknown_fstyp (no matches)
The size found after the label “size” is presented in kilobytes.
You can convert to sectors by multiplying by 2.

———–

To calculate the size of a volume, use vxprint, and look for the
“len”. The volume length is in sectors. Convert to kilobytes
by dividing by 2.

————-

Volume Growth Procudure:
1) You can use vxassist to estimate the max size of
a given volume based on the disks you wish to add:
ex: # vxassist -g rootdg maxgrow vol01 disk01 disk02 disk03

2) Next, actually grow the volume (NOT THE FS) via the
command (assuming maxgrow outputed 10639360 as the maxsize):
ex:# vxassist -g rootdg growto vol01 10639360 disk01 disk02 disk03

3) Now VxVM grinds away, monitor with vxtask.

4) Now Grow the Filesystem, for UFS use:
# /usr/lib/fs/ufs/mkfs -F ufs -M /export /dev/vx/rdsk/rootdg/vol01 10639360

for VXFS ufs:
# /usr/lib/fs/vxfs/fsadm -b 10639360 -r /dev/vx/rdsk/rootdg/vol01 /mnt
—————————————————————

5) Done!

———-

Changing User/Group of a Raw Volume: (ex:)
vxedit -g xxxdg set group=dba data_vol_123
vxedit -g xxxdg set user=oracle data_vol_123

Thanks to Ben Rockwood! Cheers!

[root@localhost] /work/users> metastat -c d103
d103 p 32GB d100
d100 m 68GB d101 d102
d101 s 68GB c1t2d0s0
d102 s 68GB c1t3d0s0

[root@localhost] /work/users> metastat -p d103
d103 -p d100 -o 32 -b 58720256 -o 127926432 -b 8388608
d100 -m d101 d102 1
d101 1 1 c1t2d0s0
d102 1 1 c1t3d0s0

So from the first metastat -c d103.. that’s a mirrored 68G partition, d100 and a 32G soft partition d103.. We still have around 35G of space.

update: — someone comment please.. this information is incomplete!

There is a downside of Facebook’s popularity though. It is a large enough site that it is worthwhile for phishers to target users on this site. Facebook phishing website looks almost idential to Facebook real website.

Face book Login

From Facebook Login to Facebook proxy, we’ll be updating this page for any related and relevant news about Facebook! Since everyone is doing post about the most popular social networking site in the internet this is our own way of contributing to the fans.

Facebook.com Site Info

Tube Master usually will be displaying site info for high traffic website. Let’s put in some fast fact about Facebook.com on our Facebook Login page:

Registrar: TUCOWS INC.
Whois Server: whois.tucows.com
Referral URL: http://domainhelp.opensrs.net
Status: clientTransferProhibited, clientUpdateProhibited, serverDeleteProhibited, serverTransferProhibited, serverUpdateProhibited

Expiration Date: 2010-03-30
Creation Date: 1997-03-29
Last Update Date: 2009-07-10

Stay tuned this page will be updated for the News and Scams of Facebook.

The following general guidelines can be used to determine if a restart of NetBackup is required after making changes to the /usr/openv/netbackup/bp.conf file on a system.

• Client daemons such as bpcd, bpbkar, tar and database agents are not persistent and are called only to complete an individual backup or restore. As a result, there are no client daemons to restart. Changes to the bp.conf on a client will take effect when new job streams start, they will not affect jobs that are already started.

• Media Server daemons such as bpbrm, bptm, bpdm are not persistent and are called only to complete a backup, restore, duplication, or other operation. Changes to the bp.conf on a media server should take effect once a new backup or restore is run, they will not affect existing backups. The exception to this is any configuration value that is passed to bpbrm by a master server process such as bpsched. Note: Other Media Manager daemons such as ltid, vmd, avrd and robotic daemons on the media server read from the /usr/openv/volmgr/vm.conf file. These daemons are persistent and typically require a restart of NetBackup.

• Master server daemons bprd, bpdbm and bpjobd are persistent. As a result, these need to be restarted to recognize changes to the NetBackup configuration. The bpsched daemon is called by bprd and is continuously active until all queued jobs have completed. The bpsched daemon must be restarted if jobs are continuously active and the configuration change needs to be picked up before the queued jobs execute.

Anyway, startup scripts of NBU netbackup usually is in /etc/init.d/ aptly called netbackup, or nbuclient. You can check out the scripts also in NBU’s home, i.e /usr/openv/netbackup/bin/goodies

Got a page.. something like “Fault found by metastat” in short description in Remedy…

# metastat | grep Need
State: Needs maintenance
State: Needs maintenance

Which disk?

# metastat d9
d9: Mirror
Submirror 0: d19
State: Needs maintenance
Submirror 1: d29
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 134221440 blocks (64 GB)

Device Relocation Information:
Device Reloc Device ID
c0t2d0 Yes id1,sd@SSEAGATE_ST373307LSUN72G_3HZ6Y1EN000074312CVW
c0t3d0 Yes id1,sd@SSEAGATE_ST373307LSUN72G_3HZ6Y46Y0000743249BK


Check for hard errors to verify if this disk can really be replaced… if it passed (on your criteria), you can try re-syncing it…

c# metareplace -e d9 c0t2d0s5
d9: device c0t2d0s5 is enabled

Verify that it’s doing what it is expected..

# metastat d9
d9: Mirror
Submirror 0: d19
State: Resyncing
Submirror 1: d29
State: Okay
Resync in progress: 0 % done
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 134221440 blocks (64 GB)

And we wait…..