05-05-2005
Do you have any kind of tape backups? Other than restoral from a backup, you may have to rebuild it..
9 More Discussions You Might Find Interesting
1. Solaris
When I installed the SOLARIS 10 OS first time, the desktop would not start up, this was because of network setup. Reinstalled worked. After a week due to some problem I had to reinstall OS, installation went fine and but when i reboot I get this error.
cannot find mis/krtld
boot error loading... (0 Replies)
Discussion started by: johncy_j
0 Replies
2. Solaris
I'm running solaris 2.5.1. My main development server is DEAD, i can't even boot off the cdrom, it powers up, acts like it is starting the boot process but then says cannot find boot device. I've done the search here on this site and saw the other posts, but at the ok prompt it won't even let me... (3 Replies)
Discussion started by: kymberm
3 Replies
3. Filesystems, Disks and Memory
Hi,
Here is some of the setup information on system:
Tru64 UNIX OS and Two Hard Drives installed. One drive is boot drive and other is spare (Spare drive currently has some back up information on it). here is just a couple of the device/partition/mount points on boot drive.
/dev/rz0a on... (4 Replies)
Discussion started by: willirb1
4 Replies
4. Solaris
Hi All,
I have installed Solaris 10 on my AMD 64 3000+ system. I was playing with grub commands eeprom and bootadm commands. I screwed my boot-file and now am unable to boot the system. Gets error msg as "panic: cannot open /kernel/amd64/unix". I booted the system is filesafe and tried update the... (2 Replies)
Discussion started by: Manjunath K V
2 Replies
5. SCO
hi
SCO Unix 5.0.6 doesn't boot due to this problem:
not a directory
boot not found
cannot open
stage 1 boot failure: error loading hd (40)/boot
Knows someone howto solve it? (16 Replies)
Discussion started by: ccc
16 Replies
6. Boot Loaders
Hello,
I have kubuntu on my laptop and now I decided to switch to Windows 7. I made the bios settings properly (first choice is boot from cd\vd) but I see the error
" reboot and select proper Boot device or insert Boot media in select Boot device and press a key "
I have tried CD and... (0 Replies)
Discussion started by: rpf
0 Replies
7. Solaris
I am trying to install Solaris x86 using the Jumpstart server. I run the add_install_client command with appropriate options, and reboot my x86 Target box. The installation starts fine and unattended. After the installation completes and the target goes for a re-boot, it does not boot from the HDD... (9 Replies)
Discussion started by: hemalsid
9 Replies
8. Solaris
Hi Solaris 10 Experts,
I am wondering what is the correct syntax to edit in Grub when trying to specify the local ZFS boot disk while booting up from a Solaris 10 x86 64bits DVD installation disk. In other word, I try to boot up from local disk without removing the Solaris installation disk... (0 Replies)
Discussion started by: gjackson123
0 Replies
9. Solaris
Hello,
I have a problem with my machine that won't boot properly.
The story is that I installed a software called apcupsd, which is a control application for my APC battery UPS. I have used version 3.14.10 earlier, but as part of restoring my previously crashed os harddrive I wanted to... (18 Replies)
Discussion started by: Zorken
18 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)