@ bartus11, i have checked the / var/ adm/messages and found what you were saying and that is "wrong magic number", the output of last 100 lines is as follows.
Code:
Jan 23 11:53:20 db19 genunix: [ID 936769 kern.info] ssd100 is /scsi_vhci/ssd@g60a98000572d51384b4a686a3333376e
Jan 23 11:53:20 db19 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60a98000572d51384b4a686a3333376e (ssd100):
Jan 23 11:53:20 db19 Corrupt label; wrong magic number
Jan 23 11:53:20 db19 genunix: [ID 487590 kern.warning] WARNING: Page83 data not standards compliant NETAPP LUN 7320
Jan 23 11:53:20 db19 genunix: [ID 834635 kern.info] /scsi_vhci/ssd@g60a98000572d51384b4a686a3333376e (ssd100) multipath status: degraded, path /pci@0,600000/pci@0/pci@9/SUNW,qlc@0/fp@0,0 (fp0) to target address: w2102000e770064b5,14 is online Load balancing: round-robin
Jan 23 11:53:20 db19 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60a98000572d51384b4a686a3333376e (ssd100):
Jan 23 11:53:20 db19 Corrupt label; wrong magic number
Jan 23 11:54:23 db19 statd[433]: [ID 766906 daemon.warning] statd: cannot talk to statd at 10.x.x.x, RPC: Authentication error(7)
Jan 23 11:54:23 db19 last message repeated 7 times
Jan 23 11:57:35 db19 genunix: [ID 487590 kern.warning] WARNING: Page83 data not standards compliant NETAPP LUN 7320
Jan 23 11:57:35 db19 last message repeated 20 times
Jan 23 11:57:35 db19 genunix: [ID 834635 kern.info] /scsi_vhci/ssd@g60a98000572d51384b4a686a3333376e (ssd100) multipath status: optimal, path /pci@0,600000/pci@0/pci@9/SUNW,qlc@0/fp@0,0 (fp0) to target address: w2104000e770064b5,14 is online Load balancing: round-robin
Jan 23 11:58:06 db19 CLSD: [ID 770310 daemon.notice] The clock on host db19 has been updated by the Cluster Time Synchronization Service to be synchronous with the mean cluster time.
Jan 23 11:59:53 db19 statd[433]: [ID 766906 daemon.warning] statd: cannot talk to statd at 10.x.x.x, RPC: Authentication error(7)
Jan 23 12:05:23 db19 last message repeated 15 times
Jan 23 12:10:47 db19 CLSD: [ID 770310 daemon.notice] The clock on host db19 has been updated by the Cluster Time Synchronization Service to be synchronous with the mean cluster time.
Jan 23 12:10:53 db19 statd[433]: [ID 766906 daemon.warning] statd: cannot talk to statd at 10.x.x.x, RPC: Authentication error(7)
Jan 23 12:10:53 db19 last message repeated 7 times
Jan 23 12:16:23 db19 statd[433]: [ID 766906 daemon.warning] statd: cannot talk to statd at 10.x.x.x, RPC: Authentication error(7)
Jan 23 12:16:23 db19 last message repeated 7 times
now after running the cfgadm -al i run format command but do not see it but in the /var/adm/messages i see "wrong magic number" but don't have nay idea what does it mean
An application running on HP-UX constantly generates new text log files ( I think using logpipe ). Any new file created requires to be ftp'ed to an offline server, however I want to make sure that the current file being written should not be transferred.
For examples consider the following files... (3 Replies)
Hi Friends,
I have to create a new log file everyday and append it with content based on some keywords found in another log file.
Here is what I have tried so far...
grep Error /parentfolder/someLogFile.log >> /parentfolder
/Archive/"testlogfile_error_`date '+%d%m%y'`.txt"
grep error... (6 Replies)
Hi,
I need to create new directory by increasing the number by 1 of extracted lastly created directory.
e.g.
Log\out_log_1\
Log\out_log_2\
Log\out_log_3\
become
Log\out_log_1\
Log\out_log_2\
Log\out_log_3\
Log\out_log_4\
Can anyone help how to do it in c-shell... (3 Replies)
Hi all,
In linux how to create a directory with specified size, so that it can be used only up to the mentioned size.
Actually my question is, whether we can do directory quota in linux.
mounting the directory in a partiton will do that, but do we have any other option... (1 Reply)
hi all,
i have added new LUN to Redhat 5. i have already scanned LUN devices and it is confirmed that Kernel sees the newly added LUN's. i have used /proc/partitions and verified that my disks are there.
However, i cannot find my disk using fdisk -l command. I am not sure what did i... (2 Replies)
hello everyone,
I am new to perl script and trying to develop a script as follows.
I am trying to Create an array for storing all file names. I am trying to copy $libs into "scratch". however i am unable to do so. Please suggest..
#!/usr/bin/perl
use File::Copy;
#use... (5 Replies)
Hi ,
I have created one new lun in my SAN storage and make it visible to my HP servers , but the fdisk -l output is somehow confusing. Do not know what to do next ----------
fdisk -l /dev/sdo1
Disk /dev/sdo1 (Sun disk label): 64 heads, 32 sectors, 10238 cylinders
Units =... (7 Replies)
AIX 7.1
New to WPAR, hopefully just missing something simple here.
Creating the WPAR like this.....
(The box where the WPAR is hosted does have an iscsi protocol device)
mkwpar -h wpar08 -l -n wpar08 -N interface=en0 address=xxx.xx.xx.xxx netmask=255.255.255.0 -D devname=/dev/iscsi0 -D... (0 Replies)
Hi
I am not familiar with the linux, but I was asked to create a file system on a LUN from the NetApp that was mapped to the linux server.
The server is runing:
uname -a
Linux localhost.localdomain 2.6.18-92.el5 #1 SMP Tue Apr 29 13:16:15 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux
and now... (6 Replies)
Hi
I need to identify a newly attached LUN from NetApp on a linuxserver running uname -o
GNU/Linux
I have first run the df -h and got the following:
df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg_outsystemdb-lv_root
50G 2.7G 45G ... (3 Replies)
Discussion started by: fretagi
3 Replies
LEARN ABOUT XFREE86
auth_attr
auth_attr(4) File Formats auth_attr(4)NAME
auth_attr - authorization description database
SYNOPSIS
/etc/security/auth_attr
DESCRIPTION
/etc/security/auth_attr is a local source for authorization names and descriptions. The auth_attr file can be used with other authorization
sources, including the auth_attr NIS map and NIS+ table. Programs use the getauthattr(3SECDB) routines to access this information.
The search order for multiple authorization sources is specified in the /etc/nsswitch.conf file, as described in the nsswitch.conf(4) man
page.
An authorization is a right assigned to users that is checked by certain privileged programs to determine whether users can execute
restricted functionality. Each entry in the auth_attr database consists of one line of text containing six fields separated by colons (:).
Line continuations using the backslash () character are permitted. The format of each entry is:
name:res1:res2:short_desc:long_desc:attr
name The name of the authorization. Authorization names are unique strings. Construct authorization names using the following
convention:
prefix. or prefix.suffix
prefix Everything in the name field up to the final dot (.). Authorizations from Sun Microsystems, Inc. use solaris as a
prefix. To avoid name conflicts, all other authorizations should use a prefix that begins with the reverse-order
Internet domain name of the organization that creates the authorization (for example, com.xyzcompany). Prefixes
can have additional arbitrary components chosen by the authorization's developer, with components separated by
dots.
suffix The final component in the name field. Specifies what is being authorized.
When there is no suffix, the name is defined as a heading. Headings are not assigned to users but are constructed
for use by applications in their GUIs.
When a name ends with the word grant, the entry defines a grant authorization. Grant authorizations are used to support
fine-grained delegation. Users with appropriate grant authorizations can delegate some of their authorizations to others.
To assign an authorization, the user needs to have both the authorization itself and the appropriate grant authorization.
res1 Reserved for future use.
res2 Reserved for future use.
short_desc A short description or terse name for the authorization. This name should be suitable for displaying in user interfaces,
such as in a scrolling list in a GUI.
long_desc A long description. This field can explain the precise purpose of the authorization, the applications in which it is used,
and the type of user that would be interested in using it. The long description can be displayed in the help text of an
application.
attr An optional list of semicolon-separated (;) key-value pairs that describe the attributes of an authorization. Zero or more
keys may be specified. The keyword help identifies a help file in HTML.
EXAMPLES
Example 1: Constructing a Name
In the following example, the name has a prefix (solaris.admin.usermgr) followed by a suffix (read):
solaris.admin.usermgr.read
Example 2: Defining a Heading
Because the name field ends with a dot, the following entry defines a heading:
solaris.admin.usermgr.:::User Accounts::help=AuthUsermgrHeader.html
Example 3: Assigning Separate Authorizations to Set User Attributes
In this example, a heading entry is followed by other associated authorization entries. The entries below the heading provide separate
authorizations for setting user attributes. The attr field for each entry, including the heading entry, assigns a help file. The applica-
tion that uses the help key requires the value to equal the name of a file ending in .htm or .html:
solaris.admin.usermgr.:::User Accounts::help=AuthUsermgrHeader.html
solaris.admin.usermgr.pswd:::Change Password::help=AuthUserMgrPswd.html
solaris.admin.usermgr.write:::Manage Users::help=AuthUsermgrWrite.html
Example 4: Assigning a Grant Authorization
This example assigns to an administrator the following authorizations:
solaris.admin.printer.grant
solaris.admin.printer.delete
solaris.admin.printer.modify
solaris.admin.printer.read
solaris.login.enable
With the above authorizations, the administrator can assign to others the solaris.admin.printer.delete, solaris.admin.printer.modify, and
solaris.admin.printer.read authorizations, but not the solaris.login.enable authorization. If the administrator has both the grant autho-
rization, solaris.admin.printmgr.grant, and the wildcard authorization, solaris.admin.printmgr.*, the administrator can grant to others any
of the printer authorizations. See user_attr(4) for more information about how wildcards can be used to assign multiple authorizations
whose names begin with the same components.
Example 5: Authorizing the Ability to Assign Other Authorizations
The following entry defines an authorization that grants the ability to assign any authorization created with a solaris prefix, when the
administrator also has either the specific authorization being granted or a matching wildcard entry:
solaris.grant:::Grant All Solaris Authorizations::help=PriAdmin.html
Example 6: Consulting the Local Authorization File Ahead of the NIS Table
With the following entry from /etc/nsswitch.conf, the local auth_attr file is consulted before the NIS table:
auth_attr:files nisplus
FILES
/etc/nsswitch.conf
/etc/user_attr
/etc/security/auth_attr
SEE ALSO getauthattr(3SECDB), getexecattr(3SECDB), getprofattr(3SECDB), getuserattr(3SECDB), exec_attr(4), nsswitch.conf(4), user_attr(4)NOTES
When deciding which authorization source to use, keep in mind that NIS+ provides stronger authentication than NIS.
Because the list of legal keys is likely to expand, any code that parses this database must be written to ignore unknown key-value pairs
without error. When any new keywords are created, the names should be prefixed with a unique string, such as the company's stock symbol, to
avoid potential naming conflicts.
Each application has its own requirements for whether the help value must be a relative pathname ending with a filename or the name of a
file. The only known requirement is for the name of a file.
The following characters are used in describing the database format and must be escaped with a backslash if used as data: colon (:), semi-
colon (;), equals (=), and backslash ().
SunOS 5.10 9 Jan 2002 auth_attr(4)