Command:

grep -H ServerMaintenanceMode=dword:1 /<path>/<port_number>/PortRegistry.reg

dword:1 = Normal operation

dword:2 = Set server to read-only mode

dword:3 = block all read and write access to server

Step 1 – Identify OS:

1. Freenas – FreeBSD based , i like FreeBSD because it was the core for Netapp too.

2. Openfiler – CentOS based, customized for NAS.

3. Fedora + Samba

I picked number 3 which is Fedora + Samba , as i still need my NAS OS to be a multi purpose server and i love YUM~

Step2 – Hardware

1. 2 years old HP 110 Netbook

2. 2TB Seagate External Harddisk

Finally…. the combination!

HP 2 years old 110

2TB Seagate External Disk

Fedora 15

Output:
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Collis Drop
e4a 9000 none none 2007724074 1 2991841358 0 0 0

0 is the one you are looking for.

[root@linux tiwlim]# rsh filerDest snapvault stop filerDest:/vol/volume_A_Dataset_new_backup_1/t28lp_ip
Stopping /vol/volume_A_Dataset_new_backup_1/t28lp_ip is permanent.
The secondary qtree will be deleted.
Further incremental updates will be impossible.
Data already stored in snapshots will not be deleted.
This may take a long time to complete.
Are you sure you want to do this? y
Snapvault configuration for the qtree has been deleted.


So the mission for today is to create the write and delete test for my environment.

Local machine  —-COPY—>  Mounted filesystem in NAS

Why i am doing so? to get a baseline for my write and delete operation.I will make use of “time” command to get total runtime for the script to complete the operation. So here goes the simple script(Feel free to provide your code if you have idea, i am a noob in python:) )

BTW, Nanako is just an echo.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41

#!/usr/bin/python
import os
import shutil
 
#set source path & file name
src = "/usr2/"
file_name = "testfile.txt"
source_file_path = src + file_name
 
#set destination path
dest = "/data/tingwei/test_copy/"
 
#set number of copies for the copying progress
copies = 1000
dir_copies = 10
 
for x in range(dir_copies):
    dirname = dest + str(x)
    if not os.path.isdir(dirname):
        os.mkdir(dirname)
        print "Nanako: mkdir " + str(dirname)
#start progress
        print "Nanako: Ready to copy " + `copies` + " files."
        for i in range(copies):
                new_file_name = file_name + `i`
                dest_file_path = dirname + "/" + new_file_name
                shutil.copyfile (source_file_path, dest_file_path)
 
print "Nanako: Done copying " + `copies` + " files."
print "Nanako: Preparing to cleanup " + dest
 
#this line is to remove the files & directories created
for x in os.listdir(dest):
   shutil.rmtree(os.path.join(dest,x))
 
#just in case you want to see is there any left over in the destination
def listdir_fullpath(d):
    return [os.path.join(d, f) for f in os.listdir(d)]
 
for i in listdir_fullpath(dest):
    print i

Below is just the example output i have for references:
I am copying from a FAS3170 to FAS960
Directory size: 1.5TB
~45MBps!!!!
Time taken: 9 hours 15 minute
Ndmpcopy: filerA: Log: DUMP: dumping (Pass V) [ACLs]
Ndmpcopy: filerA: Log: DUMP: 1563223738 KB
Ndmpcopy: filerB: Log: RESTORE: RESTORE IS DONE
Ndmpcopy: filerB: Log: RESTORE: The destination path is /vol/vol_restore/re store/
Ndmpcopy: filerB: Notify: restore successful
Ndmpcopy: filerA: Log: DUMP: DUMP IS DONE
Ndmpcopy: filerA: Log: DUMP: Deleting “/vol/fc_loan/../snapshot_for_ backup.195″ snapshot.
Ndmpcopy: filerA: Notify: dump successful
Ndmpcopy: Transfer successful [ 9 hours 15 minutes 47 seconds ]
Ndmpcopy: Done

We are old and small , but still useful!!

Every time when there  is new pendrive/thumbdrive with larger released in the market, you will buy it for your mp3, movie, porn, iso…..junk files.  It is fun to have small little tiny things with more capacity. End up you will have bunch of pendrive laying around your offices.

I love to reuse the old devices for other purposes. I have few suggestion on for the old pendrive:

1. Load Linux into pendrive and apply it as rescue disk. Suggest Backtrack 3 on a 1GB pendrive.
2. Backup device for your Linux and Windows PC

For point number 1 , i have my 1GB pendrive loaded with backtrack3 and Fedora. Backtrack3 is very useful when you need to :

• Reset windows local administrator password
• Check volume group data in Live CD mode
• Copy data from a dead OS(both windows and Linux)
• many more……

Point number 2 is my favorite part. I have 512GB mounted to my PC as my permanent backup device for my critical documents. You will need:

1.Cygwin installed with rsync

-Cygwin is a powerful opensource developed to simulate *nix environment. You are able to use *nix command in windows and it is powerful.

-rsync is a simple yet powerful script widely used in *nix for sync process.  Please read http://en.wikipedia.org/wiki/Rsync for more info.

2. Simple script(bak.bat) to trigger for backup with Scheduler.

bak.bat content

Scheduled Task in Windows XP

@ECHO OFF
rsync -avz –delete /cygdrive/c/’Documents and Settings’/tiwlim/’My Documents’/NCS /cygdrive/x
touch /cygdrive/x/done.flag

Line 1

rsync -avz –delete /cygdrive/c/’Documents and Settings’/tiwlim/’My Documents’/NCS /cygdrive/x

-avz means copy everything from source (including the permission and display the output).

–delete means compare source and destination, the destination must have whatever source is having. EG: if destination has b.txt and source does not has b.txt , b.txt will be deleted in destination.

/cygdrive/c/ is the c drive.

/cygdrive/x is my pendrive mounted to “My Computer” as X drive.

Line 2

touch /cygdrive/x/done.flag

create a done.flag once the rsync is completed.This is to let you know when is the last update.

Most of the time, the document did not consume much space. I have only 512MB pendrive mounted as my backup devices.

Trying to google around for SUN OS single mode (without cd) boot up so i can run fsck on root volume. This is the finding i have for SunOS 5.1 i386 after combining all article read.

Run fsck in SunOS 5.1

1. Boot into single mode

reboot — -m milestone=”none”

2. run

fsck -F ufs /dev/rdsk/c0t0d0s0

Result:

** phase 1 – Check Blocks and Sizes
** phase 2 – Check Pathnames
** phase 3 – Check Connectivity
** phase 4 – Check Reference Counts
** phase 5 – Check Cylinder Groups

I am safe, no bad superblock or sector. However, if you are running into trouble like : corrupted super block

newfs -Nv /dev/rdsk/c0t0d0s0

to obtain the block number of Superblock backup’s. Then finally

fsck -F ufs -o -b=32 /dev/rdsk/c0t0d0s0

*When you created new file system, alternate superblock was created as well, we are using this technique to repair bad superblock.

I will need to use smartd to scan the harddisk in SUN. write this on next post later on.

A:

You will need to ensure you have spaces in volume group. Assuming the VG name is : VolGroup00.

[root@linux1 data]# vgdisplay
— Volume group —
VG Name               VolGroup00
System ID
Format                lvm2
Metadata Areas        1
Metadata Sequence No  10
VG Access             read/write
VG Status             resizable
MAX LV                0
Cur LV                8
Open LV               8
Max PV                0
Cur PV                1
Act PV                1
VG Size               1.36 TB
PE Size               32.00 MB
Total PE              44703
Alloc PE / Size       28570 / 872.81 GB
Free  PE / Size       16133 / 524.16 GB
VG UUID               d2vwa2-6JHI-lTXJ-0WHg-iXhv-6COc-h01kf6

According to “Free PE/Size” you have 524.16GB left . Then you are good to proceed with the steps.

Lets check the current size of the LV you want to resize

[root@linux1 data]# df -h .
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/VolGroup00-lvdata
296G  191M  281G   1% /data

Lets start increasing the size!

[root@linux1 data]# lvextend -L+20G /dev/VolGroup00/lvdata
Extending logical volume lvdata to 320.00 GB
Logical volume lvdata successfully resized

Then resize it live!

[root@linux1 data]# resize2fs /dev/VolGroup00/lvdata
resize2fs 1.39 (29-May-2006)
Filesystem at /dev/VolGroup00/lvdata is mounted on /data; on-line resizing required
Performing an on-line resize of /dev/VolGroup00/lvdata to 83886080 (4k) blocks.
The filesystem on /dev/VolGroup00/lvdata is now 83886080 blocks long.

The final output you are looking for

[root@linux1 data]# df -h .
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/VolGroup00-lvdata
315G  195M  299G   1% /data

Easy right? The original guide in Redhat showed “ext2online” but i don’t see it in my /sbin ! Luckily my best friend google told me resize2fs is the new method Redhat you should update your documentation!