GUS |

Standard

Postfix or Sendmail specified SMTP relay host

By GUS • On 03/19/2015 • In Unix/Linux • 1 min read

####POSTFIX####

# vi /etc/postfix/main.cf

specify SMTP relay host

relayhost = smtp-apps03.dsc.belomor.nl

# /etc/init.d/postfix restart

# tail -f /var/log/maillog

# mailx -s “TEST_MAIL_POSTFIX” -a /home/gus/log.csv [email protected] -c [email protected] < /dev/null

# tail -f /var/log/maillog

####SENDMAIL####

# cat /etc/mail/sendmail.cf | grep DS

DSsmtp-apps03.dsc.belomor.nl

# /etc/init.d/sendmail restart

# mailx -s “TEST_MAIL_SENDMAIL” -a /home/gus/log.csv [email protected] -c [email protected] < /dev/null

Done;

more

Standard

NetApp Vfiler Qtree Quotas Configuration

By GUS • On 03/19/2015 • In NetApp, Unix/Linux • 1 min read

Login to the filer:

# ssh root@reubakss005

Go to the Vfiler unit:

>vfiler context reubakss005-f01

Create new qtree:

REUBAKSS005-F01@reubakss005> qtree create /vol/f01_vol02/IronPort_logs

Check qtree on volume f01_vol02

REUBAKSS005-F01@reubakss005> qtree status f01_vol02

Volume Tree Style Oplocks Status

——– ——– —– ——– ———

f01_vol02 ntfs enabled normal

f01_vol02 IronPort_logs ntfs enabled normal

f01_vol02 qt_regulatory_SCPX_1TB ntfs enabled normal

f01_vol02 qt_team ntfs enabled normal

Edit quotas file on Vfiler’s etc path:

\\Reubakss005-f01\c$\vol\REUBAKSS005_F01_root\etc\quotas

Example of ‘quotas’ file:

/vol/f01_vol02/IronPort_logs tree 1024G

Then you should ‘restart’ quotas on Vfiler volume to get new resized/edited quota work.

Quotas initializing will take about 20-30 seconds…

REUBAKSS005-F01@reubakss005> quota status f01_vol02

f01_vol02: quotas are on.

REUBAKSS005-F01@reubakss005> quota off f01_vol02

REUBAKSS005-F01@reubakss005> quota on f01_vol02

REUBAKSS005-F01@reubakss005> quota status f01_vol02

f01_vol02: quotas are initializing (33% done).

REUBAKSS005-F01@reubakss005> quota status f01_vol02

f01_vol02: quotas are initializing (38% done).

REUBAKSS005-F01@reubakss005> quota status f01_vol02

f01_vol02: quotas are initializing (42% done).

REUBAKSS005-F01@reubakss005> quota status f01_vol02

f01_vol02: quotas are initializing (45% done).

REUBAKSS005-F01@reubakss005> quota status f01_vol02

f01_vol02: quotas are initializing (49% done).

REUBAKSS005-F01@reubakss005> quota status f01_vol02

f01_vol02: quotas are initializing (54% done).

REUBAKSS005-F01@reubakss005> quota status f01_vol02

f01_vol02: quotas are initializing (58% done).

REUBAKSS005-F01@reubakss005> quota status f01_vol02

f01_vol02: quotas are initializing (64% done).

REUBAKSS005-F01@reubakss005> quota status f01_vol02

f01_vol02: quotas are initializing (69% done).

REUBAKSS005-F01@reubakss005> quota status f01_vol02

f01_vol02: quotas are initializing (74% done).

REUBAKSS005-F01@reubakss005> quota status f01_vol02

f01_vol02: quotas are initializing (78% done).

REUBAKSS005-F01@reubakss005> quota status f01_vol02

f01_vol02: quotas are on.

Map as a network drive newly created/exported qtree ‘IronPort_logs’ to check…

##########################################################################################

add ftpproxy user with default group ‘users’ on Vfiler unit example:

REUBAKSS005-F01@reubakss005> useradmin user add ftpproxy -c “FTP USER LOGS” -g users

New password:

Retype new password:

User <ftpproxy> added.

REUBAKSS005-F01@reubakss005> Wed Mar 18 13:54:45 AZT [REUBAKSS005-F01@reubakss005:useradmin.added.deleted:info]: The user ‘ftpproxy’ has been added.

more

Standard

Linux Software RAID | Mdadm | QNAP| BusyBox | Notes

By GUS • On 03/05/2015 • In Unix/Linux • 1 min read

This read-only file contains information about the status of currently running array and shows rebuilding speed:

# cat /proc/mdstat

Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [multipath]
md0 : active raid10 sdc3[0] sdk3[10] sdf3[9] sde3[12] sdi3[13] sdh3[14] sdg3[4] sda3[3] sdb3[2] sdd3[1]
17572185216 blocks super 1.0 64K chunks 2 near-copies [12/10] [UUUUUUU_UUU_]
[=============&gt;.......] resync = 69.7% (12249957440/17572185216) finish=462.0min speed=191956K/sec
bitmap: 8/9 pages [32KB], 1048576KB chunk

To see your Linux kernel speed limits imposed on the RAID reconstruction use:

cat /proc/sys/dev/raid/speed_limit_max
200000
cat /proc/sys/dev/raid/speed_limit_min
5000

To increase speed, enter:

echo VALUE &gt; /proc/sys/dev/raid/speed_limit_min
echo VALUE &gt; /proc/sys/dev/raid/speed_limit_maxT

To provide details about /dev/md0 raid arrray including status and health report:

# mdadm --detail /dev/md0

/dev/md0:
Version : 1.0
Creation Time : Tue May 29 14:55:47 2012
Raid Level : raid10
Array Size : 17572185216 (16758.14 GiB 17993.92 GB)
Used Dev Size : 2928697536 (2793.02 GiB 2998.99 GB)
Raid Devices : 12
Total Devices : 10
Persistence : Superblock is persistent

Intent Bitmap : Internal

Update Time : Thu Mar 5 02:10:48 2015
State : active, degraded, resyncing
Active Devices : 10
Working Devices : 10
Failed Devices : 0
Spare Devices : 0

Layout : near=2
Chunk Size : 64K

Resync Status : 69% complete

Name : 0
UUID : ce9a3c83:2a4b6b63:413f682e:923f6790
Events : 11836407

Number Major Minor RaidDevice State
0 8 35 0 active sync set-A /dev/sdc3
1 8 51 1 active sync set-B /dev/sdd3
2 8 19 2 active sync set-A /dev/sdb3
3 8 3 3 active sync set-B /dev/sda3
4 8 99 4 active sync set-A /dev/sdg3
14 8 115 5 active sync set-B /dev/sdh3
13 8 131 6 active sync set-A /dev/sdi3
14 0 0 14 removed
12 8 67 8 active sync set-A /dev/sde3
9 8 83 9 active sync set-B /dev/sdf3
10 8 163 10 active sync set-A /dev/sdk3
22 0 0 22 removed

# mdadm -D /dev/md0 ##SAME AS ABOVE

To do real-world disk write test in linux is:

# hdparm -t /dev/md0

/dev/md0:
Timing buffered disk reads: 1142 MB in 3.01 seconds = 379.96 MB/sec

more