Sponsored Content
Full Discussion: Recovering a failed system
Operating Systems AIX Recovering a failed system Post 302345371 by aixpank on Wednesday 19th of August 2009 04:48:52 AM
Old 08-19-2009
Quote:
Originally Posted by bakunin
mksysb is basically a "savevg rootvg", so there is no need to exclude such mount points because the backup process would stop on VG boundaries anyways. If you haven't included the mount points you will have to manually recreate them. Write a script which does that for you, complete with ownership, rights, filemodes, etc., so you could use it to restore them in case you need them again.

I hope this helps.

bakunin
Thanks for your reply bakunin, but you haven't answered my requirement.
See I have a mksysb which is not containing my application mount point as it was taken with excluding those mount point due to size contraints.

Now I want to recover the system with those mount points. System is not booting.

This is the scenario, now pls suggest how can I restore my system along with those mount points. I have a spare disks on which I can restore the mksysb, but then what abt those application mount point, how I will be able to recover them from those failed disk.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

/: write failed, file system full

Sun server 4 Getting message /: write failed, file system full. Okay so the problem seems obvious. The file system is full. This server is used for DNS and DHCP on a T1 connected WAN. I can't get it to quit displaying the same message as above, even when powered down and restarted. So... (1 Reply)
Discussion started by: lancest
1 Replies

2. SCO

HELP! Recovering system from New Orleans!!

I am helping a company recover a system that is SCO OS 5.0.5 - they have their backup media, cd copies of SCO, but they do not have their license keys to install and SCO is being difficult in validating their license. Does anyone have an install license key for 5.0.5 that they would be willing... (1 Reply)
Discussion started by: ggraham
1 Replies

3. AIX

Trying to back up my system and failed(with smit)

1. creating information file (/image.data) for rootvg ok! 2. creating tape boot image bosboot : dd failed to copy /dev/rmt1.1. bosboot: WARNING! bosboot failed - do not attempt to boot device mksysb: Attempt to create a bootable tape failed: bosboot -d /dev/rmt1.1 -a failed... (1 Reply)
Discussion started by: fla22
1 Replies

4. Filesystems, Disks and Memory

Is it possible that recovering a disk with jffs2 file system ?

Is it possible that recovering a disk with jffs2 file system ? (1 Reply)
Discussion started by: s. murat
1 Replies

5. IP Networking

The system function gethostbyname() failed to find the client's host name

As we are facing issue with this server connection. The error is: The system function gethostbyname() failed to find the client's host name. how can i check if the server "server1" is able to resolve the client hostname (hosts / dns)? i can ping the client from server. any... (1 Reply)
Discussion started by: jinslick25
1 Replies

6. Solaris

Recovering from corrupt /etc/system file

Hi I would like to know one thing while recovering from corrupt /etc/system file. For that we have to do at ok> boot -a when system ask for system file we give /dev/null. Could any one tell me what /dev/null value will do in this case. Regards (1 Reply)
Discussion started by: sb200
1 Replies

7. UNIX for Advanced & Expert Users

System call failed with 127 .. after 500 times when called in loop

Hi Experts, I have a code like this. ===== #include.... int main() { int count = 0; while(1){ printf("\n Interation number is: %d \n ",count); rv = system(" test.sh > log.txt " ); if (-1 == rv) { printf("Could not generate static log: error... (12 Replies)
Discussion started by: binnyjeshan
12 Replies

8. Solaris

Solaris 10 luupgrade flash archive file system creation failed

Hey guys, I'm attempting to migrate us to a new box. First problem I had was the change in architecture going from sun4u to sun4v, we have a Sun M5000 and are moving to a Fujitsu M10-4. I figured out how to make the flash archive work between architectures. Now I appear to be running into an... (2 Replies)
Discussion started by: kaledragule
2 Replies

9. Solaris

Recover failed system disk

I have an oldish Solaris 10 system (SunFire x4240), which due to a recent heating event in the server room, lost it's system disk. I have rsync backups of all the other (data) disks, but apparently I do not have a backup of /. :-( I can start the machine up in failsafe mode, but running fsck on... (4 Replies)
Discussion started by: jj5406
4 Replies

10. Infrastructure Monitoring

Failed to read from eventlog: 31: A device attached to the system is not functioning.

Hello Team, I am getting below error on nagios to monitor windows Server 2012. Failed to read from eventlog: 31: A device attached to the system is not functioning. basically we are monitoring Eventlog file for server reboot or unexpected shutdown. Could you please help here. What could be... (0 Replies)
Discussion started by: ghpradeep
0 Replies
lofs(7FS)                                                          File Systems                                                          lofs(7FS)

NAME
lofs - loopback virtual file system SYNOPSIS
#include <sys/param.h> #include <sys/mount.h> int mount (const char* dir, const char* virtual, int mflag, lofs, NULL, 0); DESCRIPTION
The loopback file system device allows new, virtual file systems to be created, which provide access to existing files using alternate pathnames. Once the virtual file system is created, other file systems can be mounted within it, without affecting the original file sys- tem. However, file systems which are subsequently mounted onto the original file system are visible to the virtual file system, unless or until the corresponding mount point in the virtual file system is covered by a file system mounted there. virtual is the mount point for the virtual file system. dir is the pathname of the existing file system. mflag specifies the mount options; the MS_DATA bit in mflag must be set. If the MS_RDONLY bit in mflag is not set, accesses to the loop back file system are the same as for the underlying file system. Otherwise, all accesses in the loopback file system will be read-only. All other mount(2) options are inherited from the underlying file systems. A loopback mount of '/' onto /tmp/newroot allows the entire file system hierarchy to appear as if it were duplicated under /tmp/newroot, including any file systems mounted from remote NFS servers. All files would then be accessible either from a pathname relative to '/' or from a pathname relative to /tmp/newroot until such time as a file system is mounted in /tmp/newroot, or any of its subdirectories. Loopback mounts of '/' can be performed in conjunction with the chroot(2) system call, to provide a complete virtual file system to a process or family of processes. Recursive traversal of loopback mount points is not allowed. After the loopback mount of /tmp/newroot, the file /tmp/newroot/tmp/newroot does not contain yet another file system hierarchy; rather, it appears just as /tmp/newroot did before the loopback mount was performed (for example, as an empty directory). Examples lofs file systems are mounted using: mount -F lofs /tmp /mnt SEE ALSO
lofiadm(1M), mount(1M), chroot(2), mount(2), sysfs(2), vfstab(4), lofi(7D) WARNINGS
Loopback mounts must be used with care; the potential for confusing users and applications is enormous. A loopback mount entry in /etc/vfstab must be placed after the mount points of both directories it depends on. This is most easily accomplished by making the loop- back mount entry the last in /etc/vfstab. SunOS 5.10 10 Apr 2001 lofs(7FS)
All times are GMT -4. The time now is 03:15 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy