Login or Register to Ask a Question and Join Our Community


UNIX for Beginners Questions & Answers

Cpio Restore didnt go to plan

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Top Forums UNIX for Beginners Questions & Answers Cpio Restore didnt go to plan
# 8  
Old 08-15-2016
You could use divvy to see the filesystem layout on your hard disk.
Code:
divvy /dev/hd0

for the proper name of the hard drive you might need to use in this command
Code:
l /dev/hd*

Unmount the /u file system and see if the lost stuff shows back up under the now visible /u directory. As mentioned above, when you mount a file system anything previously stored at the mount point directory goes away so far as the OS is concerned.

Data could be in /usr or /u. Some SCO creates that directory but it doesn't mean that the original setup used it. It is a matter of keystrokes to have it at /u. I set mine up at /user.
Last edited by rbatte1; 08-16-2016 at 10:06 AM.. Reason: Emboldened command name in text for clarity
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Cpio - input files (from list) are stored in different order inside cpio archive - why?

Due to budget constraints I have to reinvent an Enterprise backup system in a SPARC (sun4v) Solaris estate (10 & 11). (yep - reinvent wheel, fun but time consuming. Is this wise?! :confused: ) For each filesystem of interest, to try to capture a 'catalog' at the front of each cpio archive (for... (1 Reply)
Discussion started by: am115998
1 Replies

2. UNIX for Beginners Questions & Answers

CPIO Restore

Please note that using the command cpio to back up to tape was successful. Used the below command: time find /accts -print | cpio -oa --block-size=512 --format=newc --verbose -O /dev/nst0 I'm trying to restore from tape of a particular file and having issues. Below is the command to restore... (7 Replies)
Discussion started by: isoabv
7 Replies

3. Forum Support Area for Unregistered Users & Account Problems

I didnt get the activation email !!

I tried to register twice but without success ,I used the Hotmail email on both of them. Im sure I typed the correct email, because I used " copy and paste" and I did the "re-sent the activation" option (10 Replies)
Discussion started by: BaxxterHp
10 Replies

4. HP-UX

script in cron didnt run

Hi, I have script in the cron which run at predefined time everyday. If the script fails then we get the mail and a log is created. But last night the script didnt run. If the script is even started it creates log so it seems the script never ran. It has never happened before. Th... (5 Replies)
Discussion started by: shipra_31
5 Replies

5. UNIX for Dummies Questions & Answers

Unable to restore cpio archive to a directory

Hello Every one, I want to back up all passwd files to /xyz/passfiles.cpio and Then restore them to /abc directory. Here is what I wrote: find / -name passwd | cpio -oc > /tmp/passwd.cpio and to restore cd abc cpio -ium < /tmp/passwd.cpio I can not find the files restored to /abc... (2 Replies)
Discussion started by: drdigital_m
2 Replies

6. UNIX for Dummies Questions & Answers

restore cpio file

Hi, under unix aix , i had to put a catostrophic patch from an editor ... i had first made a cpio backup connected root cd /application find . –print | cpio –ocvBm > /sauvegarde/sauvegarde.cpio Does someone know the command to restore my cpio backup ? thanks in advandce to everyone ... (7 Replies)
Discussion started by: bzh35
7 Replies

7. SCO

cpio Backup and restore to spare server fails

Our company purchased a spare HP ML350 server - identical to current one in use to act as minimal downtime replacement should the inevitable happen. After install of OS 5.0.7 and restore of cpiobackup I get this message: -: Syntax error: Hostname= $inexpected The SCO licence policy... (4 Replies)
Discussion started by: moondogi
4 Replies

8. Solaris

Auto Start/Stop Didnt Work in Solaris 10

Hi...all database - 10g Rs 2 with ASM platform - Sun Solaris V890 64bit This is the step i use to auto start the database n ASM: (auto start can start but need to kill lsvcrun first) 1 dbora---script 2 start_shutdown_asm.ksh---script 3. Dbora file must be put under /etc/init.d directory... (0 Replies)
Discussion started by: adzuanamir
0 Replies

9. UNIX for Dummies Questions & Answers

Selective restore from a cpio tape archive

Hi, I use following command to restore data from my cpio tape archive: $cpio -icvd < /dev/rct0 But this'll restore all tape contents to the current path, what if I want only selected files from the tape, suppose I want /home/compdir/home2/Rev83/data/PL/01/*.* files to be restored... (8 Replies)
Discussion started by: tayyabq8
8 Replies

10. UNIX for Dummies Questions & Answers

cpio restore - relative pathname

SCO/Caldera Unixware 711 Hi Friends, I have a cpio file which was created using relative pathnames. the relative pathname is users/data/* I want to restore these files to a different directory with cpio. An example restore directory is /home/suresh Is this possible ? Can someone... (4 Replies)
Discussion started by: sureshy
4 Replies
Login or Register to Ask a Question

LEARN ABOUT DEBIAN

hpsa

HPSA(4) 						     Linux Programmer's Manual							   HPSA(4)

NAME

       hpsa - HP Smart Array SCSI driver

SYNOPSIS

       modprobe hpsa [ hpsa_allow_any=1 ]

DESCRIPTION

       hpsa is a SCSI driver for HP Smart Array RAID controllers.

   Options
       hpsa_allow_any=1:  This	option	allows	the driver to attempt to operate on any HP Smart Array hardware RAID controller, even if it is not
       explicitly known to the driver.	This allows newer hardware to work with older drivers.	Typically this is used to  allow  installation	of
       operating  systems  from media that predates the RAID controller, though it may also be used to enable hpsa to drive older controllers that
       would normally be handled by the cciss(4) driver.  These older boards have not been tested and are not supported with  hpsa,  and  cciss(4)
       should still be used for these.

   Supported Hardware
       The hpsa driver supports the following Smart Array boards:

	   Smart Array P700M
	   Smart Array P212
	   Smart Array P410
	   Smart Array P410i
	   Smart Array P411
	   Smart Array P812
	   Smart Array P712m
	   Smart Array P711m
	   StorageWorks P1210m

   Configuration Details
       To configure HP Smart Array controllers, use the HP Array Configuration Utility (either hpacuxe(8) or hpacucli(8)) or the Offline ROM-based
       Configuration Utility (ORCA) run from the Smart Array's option ROM at boot time.

FILES

   Device Nodes
       Logical drives are accessed via the SCSI disk driver (sd(4)), tape drives via the SCSI tape driver (st(4)), and the RAID controller via the
       SCSI generic driver (sg(4)), with device nodes named /dev/sd*, /dev/st*, and /dev/sg*, respectively.

   HPSA-Specific Host Attribute Files in /sys
       /sys/class/scsi_host/host*/rescan
	      This is a write-only attribute.  Writing to this attribute will cause the driver to scan for new, changed, or removed devices (e.g,.
	      hot-plugged tape drives, or newly configured or deleted logical drives, etc.)  and notify the SCSI midlayer of any changes detected.
	      Normally a rescan is triggered automatically by HP's Array Configuration Utility (either the GUI or the command-line variety); thus,
	      for logical drive changes, the user should not normally have to use this attribute.  This attribute may be useful when hot  plugging
	      devices like tape drives, or entire storage boxes containing pre-configured logical drives.

       /sys/class/scsi_host/host*/firmware_revision
	      This attribute contains the firmware version of the Smart Array.

	      For example:

		  # cd /sys/class/scsi_host/host4
		  # cat firmware_revision
		  7.14

   HPSA-Specific Disk Attribute Files in /sys
       /sys/class/scsi_disk/c:b:t:l/device/unique_id
	      This attribute contains a 32 hex-digit unique ID for each logical drive.

	      For example:

		  # cd /sys/class/scsi_disk/4:0:0:0/device
		  # cat unique_id
		  600508B1001044395355323037570F77

       /sys/class/scsi_disk/c:b:t:l/device/raid_level
	      This attribute contains the RAID level of each logical drive.

	      For example:

		  # cd /sys/class/scsi_disk/4:0:0:0/device
		  # cat raid_level
		  RAID 0

       /sys/class/scsi_disk/c:b:t:l/device/lunid
	      This  attribute contains the 16 hex-digit (8 byte) LUN ID by which a logical drive or physical device can be addressed.  c:b:t:l are
	      the controller, bus, target and lun of the device.

	      For example:

		  # cd /sys/class/scsi_disk/4:0:0:0/device
		  # cat lunid
		  0x0000004000000000

   Supported ioctl() operations
       For compatibility with applications written for the cciss(4) driver, many, but not all of the ioctls supported by the cciss(4)  driver  are
       also  supported	by  the  hpsa  driver.	 The  data  structures	used  by  these  ioctls  are  described  in  the  Linux kernel source file
       include/linux/cciss_ioctl.h.

       CCISS_DEREGDISK, CCISS_REGNEWDISK, CCISS_REGNEWD
	      These three ioctls all do exactly the same thing, which is to cause the driver to rescan for new devices.   This	does  exactly  the
	      same thing as writing to the hpsa-specific host "rescan" attribute.

       CCISS_GETPCIINFO
	      Returns PCI domain, bus, device and function and "board ID" (PCI subsystem ID).

       CCISS_GETDRIVVER
	      Returns driver version in three bytes encoded as:

		  (major_version << 16) | (minor_version << 8) |
		      (subminor_version)

       CCISS_PASSTHRU, CCISS_BIG_PASSTHRU
	      Allows "BMIC" and "CISS" commands to be passed through to the Smart Array.  These are used extensively by the HP Array Configuration
	      Utility, SNMP storage agents, etc.  See cciss_vol_status at <http://cciss.sf.net> for some examples.

SEE ALSO

       cciss(4), sd(4), st(4), cciss_vol_status(8), hpacucli(8), hpacuxe(8),

       <http://cciss.sf.net>, and Documentation/scsi/hpsa.txt and Documentation/ABI/testing/sysfs-bus-pci-devices-cciss in the Linux kernel source
       tree

COLOPHON

       This  page is part of release 3.44 of the Linux man-pages project.  A description of the project, and information about reporting bugs, can
       be found at http://www.kernel.org/doc/man-pages/.

Linux								    2012-08-05								   HPSA(4)