04-30-2008
san lv showing old fs
Hi All,
I have been working with two AIX with san and this is the first I got this minor problem on my third AIX. The san/hdisk was recreated so many times because of this problem. When I created a new vg and fs. The fs will be mounted/unmounted properly but if I query the fs on a vg with this "lsvg -l vg", the fs that will show will be the previous lv that I created but the mounted fs is the new, even with df, I will see the new lv/fs. Even when I cd to the new fs, it will change to it, but if I cd to the old fs, it will give me error with no such file or directory.
Why is that? Is my ODM corrupted?
Thanks in advance,
itik
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello all,
I have looked at the entire posting that have SAN in it and I'm still fuzzy on how SAN works. I understand that every disk array can be access from any server that needs it, but is there software that is install or NFS mount type situation. One post stated that if your format command... (7 Replies)
Discussion started by: larry
7 Replies
2. AIX
hi
We have 2 AIX nodes running with HACMP and all of them connected to SAN,
Our shared storage is shark; I need to create shared volume group and I need the HACMP take a ware of it.
Regards (1 Reply)
Discussion started by: h2aix
1 Replies
3. HP-UX
Hi, I'm going to be involved in a migration of SAN islands to one big SAN. I've not worked with SANs before and I'm not sure how to approach this. I suspect the disk devices on the HP servers are going to change, when the EVA's and servers are plugged into this new Cisco 9509 switch.
Any... (0 Replies)
Discussion started by: Hils
0 Replies
4. IP Networking
Hi
I like to learn and practice SAN, iSCSI. Could you sugges the appropriate tutorial and small tasks to practice SAN.
Thankyou (1 Reply)
Discussion started by: kingskar
1 Replies
5. Solaris
I am about to attempt to connect my sun 280R boxes to a EMC SAN.
I have Qlogic cards that came from Sun.
I am going to load traffic manager, navisphere client.
what else do i need, sun foundation suite ro somehting?
This is the first time ive ever connected to a SAN.
any help would be... (3 Replies)
Discussion started by: BG_JrAdmin
3 Replies
6. Solaris
Hi everyone,
I wonder if I can canvas any opinions or thoughts (good or bad) on SAN attaching a SUN V880/490 to an EMC Clarion SAN?
At the moment the 880 is using 12 internal FC-AL disks as a db server and seems to be doing a pretty good job. It is not I/O, CPU or Memory constrained and the... (2 Replies)
Discussion started by: si_linux
2 Replies
7. AIX
Dera all
I have error repeating for two day, when I checked the error log by errpt command:
------------------------------------------------------------------------
LABEL: SC_DISK_ERR2
IDENTIFIER: 79B0DF89
Date/Time: Wed Oct 31 02:41:36 SAUS
Sequence Number: 9000... (1 Reply)
Discussion started by: magasem
1 Replies
8. Linux
Hello everyone.
I was wondering if there is a way to increase the size on the LUN on a SAN and make the Linux kernel understand the changes without restarting?
In the past it has always been rebooted to see the new values but im sure that there is a way now for the lvm to see the Free PE in... (8 Replies)
Discussion started by: d_ark
8 Replies
9. AIX
Has anyone tried SAN to SAN mirroring on IBM DS SAN Storage.
DS5020 mentions Enhanced Remote Mirror to multi-LUN applications
I wonder if Oracle High availibility can be setup using Remote Mirror option of SAN ? (1 Reply)
Discussion started by: filosophizer
1 Replies
10. Filesystems, Disks and Memory
hi! i got a rhel 6.3 host that already have an xfs filesystem mounted from a SAN (let's call it SAN-1) whose size is 9TB.
i will be receiving another SAN (let's call it SAN-2) storage of 15TB size. this new addition is physically on another SAN storage. SAN-1 is on a Pillar storage while the new... (6 Replies)
Discussion started by: rino19ny
6 Replies
LEARN ABOUT CENTOS
strongimcv_pki---issue
PKI --ISSUE(8) strongSwan PKI --ISSUE(8)
NAME
pki --issue - Issue a certificate using a CA certificate and key
SYNOPSIS
pki --issue [--in file] [--type type] --cakey file|--cakeyid hex --cacert file [--dn subject-dn] [--san subjectAltName] [--lifetime days]
[--serial hex] [--flag flag] [--digest digest] [--ca] [--crl uri [--crlissuer issuer]] [--ocsp uri] [--pathlen len] [--nc-
permitted name] [--nc-excluded name] [--policy-mapping mapping] [--policy-explicit len] [--policy-inhibit len]
[--policy-any len] [--cert-policy oid [--cps-uri uri] [--user-notice text]] [--outform encoding] [--debug level]
pki --issue --options file
pki --issue -h | --help
DESCRIPTION
This sub-command of pki(1) is used to issue a certificate using a CA certificate and private key.
OPTIONS
-h, --help
Print usage information with a summary of the available options.
-v, --debug level
Set debug level, default: 1.
-+, --options file
Read command line options from file.
-i, --in file
Public key or PKCS#10 certificate request file to issue. If not given the key/request is read from STDIN.
-t, --type type
Type of the input. Either pub for a public key, or pkcs10 for a PKCS#10 certificate request, defaults to pub.
-k, --cakey file
CA private key file. Either this or --cakeyid is required.
-x, --cakeyid hex
Key ID of a CA private key on a smartcard. Either this or --cakey is required.
-c, --cacert file
CA certificate file. Required.
-d, --dn subject-dn
Subject distinguished name (DN) of the issued certificate.
-a, --san subjectAltName
subjectAltName extension to include in certificate. Can be used multiple times.
-l, --lifetime days
Days the certificate is valid, default: 1095.
-s, --serial hex
Serial number in hex. It is randomly allocated by default.
-e, --flag flag
Add extendedKeyUsage flag. One of serverAuth, clientAuth, crlSign, or ocspSigning. Can be used multiple times.
-g, --digest digest
Digest to use for signature creation. One of md5, sha1, sha224, sha256, sha384, or sha512. Defaults to sha1.
-f, --outform encoding
Encoding of the created certificate file. Either der (ASN.1 DER) or pem (Base64 PEM), defaults to der.
-b, --ca
Include CA basicConstraint extension in certificate.
-u, --crl uri
CRL distribution point URI to include in certificate. Can be used multiple times.
-I, --crlissuer issuer
Optional CRL issuer for the CRL at the preceding distribution point.
-o, --ocsp uri
OCSP AuthorityInfoAccess URI to include in certificate. Can be used multiple times.
-p, --pathlen len
Set path length constraint.
-n, --nc-permitted name
Add permitted NameConstraint extension to certificate.
-N, --nc-excluded name
Add excluded NameConstraint extension to certificate.
-M, --policy-mapping issuer-oid:subject-oid
Add policyMapping from issuer to subject OID.
-E, --policy-explicit len
Add requireExplicitPolicy constraint.
-H, --policy-inhibit len
Add inhibitPolicyMapping constraint.
-A, --policy-any len
Add inhibitAnyPolicy constraint.
Certificate Policy
Multiple certificatePolicy extensions can be added. Each with the following information:
-P, --cert-policy oid
OID to include in certificatePolicy extension. Required.
-C, --cps-uri uri
Certification Practice statement URI for certificatePolicy.
-U, --user-notice text
User notice for certificatePolicy.
EXAMPLES
To save repetitive typing, command line options can be stored in files. Lets assume pki.opt contains the following contents:
--cacert ca_cert.der --cakey ca_key.der --digest sha256
--flag serverAuth --lifetime 1460 --type pkcs10
Then the following command can be used to issue a certificate based on a given PKCS#10 certificate request and the options above:
pki --issue --options pki.opt --in req.der > cert.der
SEE ALSO
pki(1)
5.1.1 2013-08-12 PKI --ISSUE(8)