10-04-2002
Thanks. We had HP support on the line ( they didn't like our idea of using dd ) and when we went to do what they wanted ( boot single user - vgcfgrestore , vgchange...) they didn't hear us when we mentioned the backups were on done with Legato networker to a SUN server w/jukebox. They had us in single user with no connection to the other server. When we told them this (before anything was actually done) their response was "Oops".
Then they come back with a way of moving the data without being in single user but using pvmove (as Perderabo suggested ). Worked great for /usr but /opt and /var didn't work. Both died with i/o errors (must be where the bad blocks on the disk were at).
So we go to restore /var and /opt....networker can't find the tape volumes! Makes it look like the system had not had a full backup for over a year! (still looking into that one!)
So, we ended up creating two new logical volumes, mounting them as /newvar and /newopt and doing cpio from the old to the new....so far it's only had a few problems with certain files (we are hoping they aren't needed or if they are to copy from a dev box with the same OS/version).
Sure wish we had a real HP-UX god(dess) here - ours was let go in the last RIF (although she didn't mind as she just had twins).
Last edited by RTM; 10-04-2002 at 07:18 PM..
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
$ errpt | more
IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION
3074FEB7 0802050205 T H fscsi1 ADAPTER ERROR
B8113DD1 0802050205 T H fcs1 LINK ERROR
B8113DD1 0802050205 T H fcs1 LINK ERROR
3074FEB7 0802050205 T H fscsi0 ADAPTER ERROR
B8113DD1 ... (0 Replies)
Discussion started by: mcastill66
0 Replies
2. UNIX for Dummies Questions & Answers
I have a SunOS 5.8 server. I suspect there may be errors with one of the physical disks (based on someone reporting hearing a "clicking sound" during the night shift, however I do not hear anything this morning).
Which log would show this?
Thank you. (2 Replies)
Discussion started by: FredSmith
2 Replies
3. AIX
Hi,
I'm getting the errors below in the errpt report for a IBM Blade server. I'm guessing there's a problem with one of the disks but don't know how I can confirm this. Can anyone offer any suggestions?
Regards
Gareth (4 Replies)
Discussion started by: m223464
4 Replies
4. UNIX for Dummies Questions & Answers
Hi all, dummy here.... I have major errors on entering the shell. On login I get:
-bash: dircolors: command not found
-bash: tr: command not found
-bash: fgrep: command not found
-bash: grep: command not found
-bash: grep: command not found
-bash: id: command not found
-bash: [: =: unary... (12 Replies)
Discussion started by: wcmmlynn
12 Replies
5. Filesystems, Disks and Memory
so we have a solrais 9 system attached to an HP SAN.
we are using sssu to do snap clones every hour.
the only problem is the we get write errors on the solrais system every time we do a snap.
from /var/adm/messages
Apr 21 14:37:48 svr001 scsi: WARNING:... (0 Replies)
Discussion started by: robsonde
0 Replies
6. Shell Programming and Scripting
I am looking for some tips or suggestions in how to do the following.
1) From a Solaris server, I run the command iostat -En and receive output that is similiar to the following which shows your disks along with the cdrom/dvdrom:
c0t2d0 Soft Errors: 0 Hard Errors: 0 Transport... (1 Reply)
Discussion started by: sunsysadm2003
1 Replies
7. Solaris
Hi all.
I am seeing in one of our less-used servers that it crashed and now won't restart. I get the message 'continue with normal startup or boot into maintenance mode'.
I go into maintenance and run fsck on /usr0 (mentioned in error at restart) it then reboots but goes right back to... (3 Replies)
Discussion started by: jamie_collins
3 Replies
8. AIX
Hi,
The system is a Power6 8204 with an external storage 7031. OS is AIX 5.3. I replaced a failed disk hdisk28 and put it back to the volume group. Everything looks just fine. After the replacement, errpt has kept sending "Perm DISK OPERATION ERROR".
Other than the error, everything still... (1 Reply)
Discussion started by: aixlover
1 Replies
9. Ubuntu
Hi,
During start up I got the message "Your disk drives are being checked for errors". But it went so fast that I could read following messages.
Once logged I though I could find it in "dmesg" but nothing...
May someone know where I can find plese ? :) (3 Replies)
Discussion started by: xib.be
3 Replies
10. Solaris
Hi,
What are the initial checks needs to be done while observing hard errors on one of the hard disk drive.
Thanks,
Babu. (1 Reply)
Discussion started by: lbreddy
1 Replies
LEARN ABOUT DEBIAN
s3qllock
S3QLLOCK(1) S3QL S3QLLOCK(1)
NAME
s3qllock - Make trees on an S3QL file system immutable
SYNOPSIS
s3qllock [options] <directory>
DESCRIPTION
S3QL is a file system for online data storage. Before using S3QL, make sure to consult the full documentation (rather than just the man
pages which only briefly document the available userspace commands).
The s3qllock command makes a directory tree in an S3QL file system immutable. Immutable trees can no longer be changed in any way whatso-
ever. You can not add new files or directories and you can not change or delete existing files and directories. The only way to get rid of
an immutable tree is to use the s3qlrm command.
s3qllock can only be called by the user that mounted the file system and (if the file system was mounted with --allow-other or
--allow-root) the root user. This limitation might be removed in the future (see issue 155).
RATIONALE
Immutability is a feature designed for backups. Traditionally, backups have been made on external tape drives. Once a backup was made, the
tape drive was removed and locked somewhere in a shelf. This has the great advantage that the contents of the backup are now permanently
fixed. Nothing (short of physical destruction) can change or delete files in the backup.
In contrast, when backing up into an online storage system like S3QL, all backups are available every time the file system is mounted.
Nothing prevents a file in an old backup from being changed again later on. In the worst case, this may make your entire backup system
worthless. Imagine that your system gets infected by a nasty virus that simply deletes all files it can find -- if the virus is active
while the backup file system is mounted, the virus will destroy all your old backups as well!
Even if the possibility of a malicious virus or trojan horse is excluded, being able to change a backup after it has been made is generally
not a good idea. A common S3QL use case is to keep the file system mounted at all times and periodically create backups with rsync -a. This
allows every user to recover her files from a backup without having to call the system administrator. However, this also allows every user
to accidentally change or delete files in one of the old backups.
Making a backup immutable protects you against all these problems. Unless you happen to run into a virus that was specifically programmed
to attack S3QL file systems, backups can be neither deleted nor changed after they have been made immutable.
OPTIONS
The s3qllock command accepts the following options:
--debug
activate debugging output
--quiet
be really quiet
--version
just print program version and exit
EXIT STATUS
s3qllock returns exit code 0 if the operation succeeded and 1 if some error occurred.
SEE ALSO
The S3QL homepage is at http://code.google.com/p/s3ql/.
The full S3QL documentation should also be installed somewhere on your system, common locations are /usr/share/doc/s3ql or
/usr/local/doc/s3ql.
COPYRIGHT
2008-2011, Nikolaus Rath
1.11.1 August 27, 2014 S3QLLOCK(1)