Sponsored Content
Operating Systems Solaris Bad exchange descriptor : not able to remove files under zpool Post 302786661 by chidori on Thursday 28th of March 2013 03:04:30 AM
Old 03-28-2013
At last i restored the pool from backup
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

bad file descriptor?

Ok, I'm sure this is a total newbie question, but I think I'm in the right place, no? I'm trying to call a perl module from a cgi script - Mail::Sendmail - and my web host installed the module in a directory that doesn't seem to be accessible, at least not the way I'm trying. But I thought you... (1 Reply)
Discussion started by: ftb
1 Replies

2. Solaris

Remove the exported zpool

I had a pool which was exported and due to some issues on my SAN i was never able to import it again. Can anyone tell me how can i destroy the exported pool to free up the LUN. I tried to create a new pool on the same pool but it gives me following error # zpool create emcpool4 emcpower0c... (0 Replies)
Discussion started by: fugitive
0 Replies

3. Solaris

Can't remove a LUN from a Zpool!

I am not seeing anyway to remove a LUN from a Zpool... Am I missing something? or do i have to destroy the zpool and recreate it? (2 Replies)
Discussion started by: BG_JrAdmin
2 Replies

4. Programming

utime returning -1 BAD File DEscriptor

Hi All, First of all thanks for reading this post. In my application, I am trying to create a new message queue . I am attaching the code below. mqd_t mqopen2(const char * pName, unsigned long Flags, long maxMsg, long msgSz) {... (15 Replies)
Discussion started by: parusasi
15 Replies

5. Ubuntu

ufsdump from Solaris to ubuntu fails with bad file descriptor

Hi All I have a dedicated backup server running ubuntu 10.04, which has recently been rebuilt (same OS, just different h/w) This is used to receive ufsdump output from a number of Solaris servers, using the following syntax: ufsdump 1uf :/path/to/backup/file /fs/to/be/backed/up This has... (1 Reply)
Discussion started by: in2deep
1 Replies

6. AIX

AIX6.1 Remove file descriptor from specified process

Hi, How to release file description area from specified process. Problem is that process started - open one file ( ~2GB ) - file has been removed - process still shown that file is used by process and can't release space on filesystem. It is not allowable to kill process !!! Regs,... (3 Replies)
Discussion started by: KrzysiekPi
3 Replies

7. Shell Programming and Scripting

remove bad records.

HI I have a problem in a file .The file was generated with the wrong data in it. MAL 005158UK473BBTICK1120722 A9999999ADASCD 1120722ADD_SECURIADD_SECURI MAL 005158UK473BBU 1120722 A9999999FF000EA0B9C 1120722ADD_SECURIADD_SECURI MAL 005158UK473ISN 1120722 A9999999US005158UK43... (5 Replies)
Discussion started by: ptappeta
5 Replies

8. Shell Programming and Scripting

Error in the o/p says bad file descriptor...

grt=`sort -nr line_count.txt|head -1` while read $dline do if $grt" -eq "`wc -l combo_operncount.$dline|awk '{print $1}'`" ] then awk -F, '{print $1}' combo_operncount.$dline > FULLD7 else echo combo_operncount.$dline >> filecoll.txt fname=`cat filecoll.txt|tr -s "\n" " "` echo $fname... (6 Replies)
Discussion started by: nikhil jain
6 Replies

9. Solaris

Cannot remove disk added to zpool

I added a disk to a zpool using "zpool add diskname" My intention was mirror a zpool disk that no mirror; that is a zpool with only one disk. I did not issue the right command. Now, the disk has been added successfully but I cannot remove nor detach it as Solaris 11 thinks it has data on it... (14 Replies)
Discussion started by: LittleLebowski
14 Replies

10. UNIX for Beginners Questions & Answers

Bad file descriptor - error with sed

I'm learning SED command. And while doing that i got to this place where i'm taking a copy of my existing file. The code i used is - sed -n '/Storm/ w Storm.txt' books.txt As expected, the file 'books.txt' is read , and lines with 'Storm' is put in to the new file 'Storm.txt'. However, it also... (4 Replies)
Discussion started by: justo
4 Replies
nisrestore(1M)						  System Administration Commands					    nisrestore(1M)

NAME
nisrestore - restore NIS+ directory backup SYNOPSIS
nisrestore [-fv] backup-dir directory... nisrestore [-fv] -a backup-dir nisrestore -t backup-dir DESCRIPTION
nisrestore restores an existing backup of a NIS+ directory object that was created using nisbackup(1M). The backup-dir is the UNIX direc- tory that contains the NIS+ backup on the server being restored. The nisrestore command can be used to restore a NIS+ directory object or a complete NIS+ database. It also can be used as an "out of band" fast replication for a new replica server being initialized. The rpc.nisd(1M) daemon must be stopped before running nisrestore. The first synopsis is used to restore a single directory object or a specified list of directory objects. The directory can be partially qualified or fully qualified. The server being restored will be verified against the list of servers serving the directory. If this server is not configured to serve this object, nisrestore will exit with an error. The -f option will override this check and force the operation. The second synopsis will restore all of the directory objects contained in the backup-dir. Again, the server will be validated against the serving list for each of the directory objects in the backup-dir. If one of the objects in the backup-dir are not served by this server, nisrestore will exit with an error. The -f option will override this check and force the operation. The -a option will attempt to restore all NIS+ objects contained in the backup-dir. If any of these objects are not served by the server, nisrestore will exit with an error. If the backup-dir contains objects that are not served by the server, nisrestore must be executed with- out the -a option and the specific directory objects listed. The -f option will disable verification of the server being configured to serve the objects being restored. This option should be used with care, as data could be inadvertently restored to a server that doesn't serve the restored data. This option is required in the case of restoring a single server domain (master server only) or if the other NIS+ servers are unavailable for NIS+ lookups. The combination of options -f and -a should be used with caution, as no validation of the server serving the restored objects will be done. New replicas can be quickly added to a namespace with the nisrestore command. The steps are as follows. Configure the new replica on the master server (see nisserver(1M)): master# nisserver -R -h replica Temporarily stop the rpc.nisd server process on the new replica server: replica# svcadm disable -t network/rpc/nisplus:default Create a backup of the NIS+ database on the master, which will include the new replica information. See nisbackup(1M). The /backup will need to be exported to the new replica. See share_nfs(1M). master# nisbackup -a /backup Restore the backup of the NIS+ database on the new replica. Use the -f option if nisrestore is unable to lookup the NIS+ objects being restored. The backup should be available through nfs or similar means. See share_nfs(1M). replica# nisrestore -f -a //nfs-mnt/backup Restart the rpc.nisd(1M) process on the new replica, and the server will immediately be available for service: replica# svcadm enable network/rpc/nisplus:default OPTIONS
The following options are supported: -a Restores all directory objects included in the backup-dir partition. -f Forces the restoration of a directory without the validation of the server in the directory object's serving list. -t Lists all directory objects contained in backup-dir. -v Verbose option. Additional output will be produced upon execution of the command. OPERANDS
The following options are supported: backup-dir The UNIX directory that contains the data files for the NIS+ directory objects to be restored. directory The NIS+ directory object(s) to be restored. This can be a fully or partially qualified name. EXAMPLES
Example 1: Restoring the Directory Object on a Replica Server from a Local UFS Partition To restore the org_dir directory object of the domain foo.com on a replica server from a local ufs partition named /var/backup: replica_server# nisrestore /var/backup org_dir.foo.com. Example 2: Forcing the Restore of a Backed up NIS+ Namespace to a Replica Server From the Backup Partition To force the restore of an entire backed up NIS+ namespace to a replica server from the backup partition named /var/backup: replica_server# nisrestore -f -a /var/backup Example 3: Restoring the Subdomain on a Master Server From a Backup that Includes Other Directory Objects To restore the subdomain sub.foo.com on a master server, from a backup that includes other directory objects: master_server# nisrestore /var/backup sub.foo.com. org_dir.sub.foo.com. groups_dir.sub.foo.com. EXIT STATUS
0 Successful completion. 1 An error occurred. FILES
/backup-dir/backup_list This ASCII file contains a list of all the objects contained in this backup-dir directory. This information can be displayed with the -t option. /backup-dir/directory-object A subdirectory that is created in the backup-dir which contains the directory-object backup. /backup-dir/directory-object/data A subdirectory that contains the data files that are part of the directory-object backup. /backup-dir/directory-object/last.upd This data file contains timestamp information about the directory-object. /backup-dir/directory-object/data.dict A NIS+ data dictionary for all of the objects contained in this directory-object backup. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWnisu | +-----------------------------+-----------------------------+ SEE ALSO
svcs(1), nis+(1), nisdefaults(1), nisbackup(1M), nisserver(1M), rpc.nisd(1M), share_nfs( 1M), svcadm(1M), nisfiles(4), attributes(5), smf(5) NOTES
NIS+ might not be supported in future releases of the SolarisTM Operating Environment. Tools to aid the migration from NIS+ to LDAP are available in the Solaris 9 operating environment. For more information, visit http://www.sun.com/directory/nisplus/transition.html. The NIS+ service is managed by the service management facility, smf(5), under the service identifier: svc:/network/rpc/nisplus:default Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser- vice's status can be queried using the svcs(1) command. SunOS 5.10 13 Aug 2004 nisrestore(1M)
All times are GMT -4. The time now is 04:31 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy