/titanic_52/usr/src/cmd/tbl/ |
H A D | te.c | 75 char backup[BACKMAX]; variable 76 char *backp = backup; 84 if (backp >= backup+BACKMAX) in un1getc() 85 error(gettext("too much backup")); in un1getc() 92 if (backp>backup) in get1char()
|
/titanic_52/usr/src/test/zfs-tests/tests/functional/cli_root/zpool_import/ |
H A D | zpool_import_missing_002_pos.ksh | 120 typeset basedir backup 133 backup="" 147 [[ -n $backup ]] && \ 160 if [[ -z $backup ]] ; then 162 backup="true"
|
H A D | zpool_import_missing_001_pos.ksh | 109 typeset basedir backup 117 backup="" 133 [[ -n $backup ]] && \ 145 if [[ -z $backup ]]; then 148 backup="true"
|
/titanic_52/usr/src/contrib/ast/src/lib/libcmd/ |
H A D | cp.c | 101 "[B:backup?Make backups of files that are about to be replaced. " 102 "\b--suffix\b sets the backup suffix. The backup type is determined in " 106 "[+numbered|t?Always make numbered backups. The numbered backup " 115 "[S:suffix?A backup file is made by renaming the file to the same name " 116 "with the backup suffix appended. The backup suffix is determined in " 119 "[b?\b--backup\b using the type in the \bVERSION_CONTROL\b environment " 152 #define BAK_replace 0 /* no backup -- just replace */ 160 int backup; /* BAK member [all...] |
/titanic_52/usr/src/cmd/svc/configd/ |
H A D | restore_repository.sh | 90 this script to restore backup copies of the smf(5) repository. 173 The time of backup is given in YYYYMMDD_HHMMSS format. 175 Please enter either a specific backup repository from the above list to 180 boot restore the most recent post-boot backup 181 manifest_import restore the most recent manifest_import backup 343 echo "The backup repository has been successfully restored."
|
/titanic_52/usr/src/cmd/svr4pkg/pkginstall/ |
H A D | backup.c | 40 backup(char *path, int mode) in backup() function
|
H A D | Makefile | 29 OBJS= backup.o \
|
H A D | pkginstall.h | 58 extern void backup __P((char *path, int mode));
|
H A D | instvol.c | 1117 backup(*dstp, 1); in domerg() 1122 backup(ept->path, 0); in domerg()
|
/titanic_52/usr/src/cmd/backup/ |
H A D | Makefile | 26 # cmd/backup/Makefile 29 include Makefile.backup
|
/titanic_52/usr/src/grub/grub-0.97/stage2/ |
H A D | gpt.h | 40 grub_uint64_t backup; member
|
/titanic_52/usr/src/cmd/mailx/ |
H A D | list.c | 696 register char *cp, *cp2, *backup; in matchsubj() local 713 backup = cp2; in matchsubj() 718 cp2 = ++backup; in matchsubj()
|
/titanic_52/usr/src/cmd/fm/dicts/ |
H A D | ZFS.po | 74 msgstr "\nFor an active pool\n\nIf this error was encountered while running 'zpool import', please see\nthe section below. Otherwise, run 'zpool status -x' to determine which pool\nhas experienced a failure:\n\n\n# zpool status -x\n pool: test\n state: FAULTED\nstatus: One or more devices could not be opened. There are insufficient\n replicas for the pool to continue functioning.\naction: Attach the missing device and online it using 'zpool online'.\n see: http://illumos.org/msg/ZFS-8000-3C\n scrub: none requested\nconfig:\n\n NAME STATE READ WRITE CKSUM\n test FAULTED 0 0 0 insufficient replicas\n c0t0d0 ONLINE 0 0 0\n c0t0d1 FAULTED 0 0 0 cannot open\n\nerrors: No known data errors\n\n\nIf the device has been temporarily detached from the system, attach the\ndevice to the system and run 'zpool status' again. The pool should\nautomatically detect the newly attached device and resume functioning. You may\nhave to mount the filesystems in the pool explicitly using 'zfs\nmount -a'.\n\nIf the device is no longer available and cannot be reattached to the\nsystem, then the pool must be destroyed and re-created from a backup\nsource.\n\nFor an exported pool\n\nIf this error is encountered during a 'zpool import', it means that one\nof the devices is not attached to the system:\n\n\n# zpool import\n pool: test\n id: 10121266328238932306\n state: FAULTED\nstatus: One or more devices are missing from the system.\naction: The pool cannot be imported. Attach the missing devices and\n try again.\n see: http://illumos.org/msg/ZFS-8000-3C\nconfig:\n\n test FAULTED insufficient replicas\n c0t0d0 ONLINE\n c0t0d1 FAULTED cannot open\n\n\nThe pool cannot be imported until the missing device is attached to the\nsystem. If the device has been made available in an alternate location, use the\n'-d' option to 'zpool import' to search for devices in a different directory.\nIf the missing device is unavailable, then the pool cannot be imported.\n " 106 msgstr "\nFor an active pool\n\nIf this error was encountered while running 'zpool import', please see\nthe section below. Otherwise, run 'zpool status -x' to determine which pool\nhas experienced a failure:\n\n\n# zpool status -x\n pool: test\n state: FAULTED\nstatus: One or more devices could not be used because the the label is missing \n or invalid. There are insufficient replicas for the pool to continue\n functioning.\naction: Destroy and re-create the pool from a backup source.\n see: http://illumos.org/msg/ZFS-8000-5E\n scrub: none requested\nconfig:\n\n NAME STATE READ WRITE CKSUM\n test FAULTED 0 0 0 insufficient replicas\n c0t0d0 FAULTED 0 0 0 corrupted data\n c0t0d1 ONLINE 0 0 0\n\nerrors: No known data errors\n\n\nThe device listed as FAULTED with 'corrupted data' cannot be opened due\nto a corrupt label. ZFS will be unable to use the pool, and all data within the\npool is irrevocably lost. The pool must be destroyed and recreated from an\nappropriate backup source. Using replicated configurations will prevent this\nfrom happening in the future.\n\nFor an exported pool\n\nIf this error is encountered during 'zpool import', the action is the\nsame. The pool cannot be imported - all data is lost and must be restored from\nan appropriate backup source.\n " 138 msgstr "\nEven though all the devices are available, the on-disk data\nhas been corrupted such that the pool cannot be opened. If a recovery\naction is presented, the pool can be returned to a usable state.\nOtherwise, all data within the pool is lost, and the pool must be\ndestroyed and restored from an appropriate backup source. ZFS\nincludes built-in metadata replication to prevent this from happening\neven for unreplicated pools, but running in a replicated configuration\nwill decrease the chances of this happening in the future.\n\nIf this error is encountered during 'zpool import', see the\nsection below. Otherwise, run 'zpool status -x' to determine which\npool is faulted and if a recovery option is available:\n\n\n# zpool status -x\n pool: test\n id: 13783646421373024673\n state: FAULTED\nstatus: The pool metadata is corrupted and cannot be opened.\naction: Recovery is possible, but will result in some data loss.\n Returning the pool to its state as of Mon Sep 28 10:24:39 2009\n should correct the problem. Approximately 59 seconds of data\n will have to be discarded, irreversibly. Recovery can be\n attempted by executing 'zpool clear -F test'. A scrub of the pool\n is strongly recommended following a successful recovery.\n see: http://illumos.org/msg/ZFS-8000-72\nconfig:\n\n NAME STATE READ WRITE CKSUM\n test FAULTED 0 0 2 corrupted data\n c0t0d0 ONLINE 0 0 2\n c0t0d1 ONLINE 0 0 2\n\n\nIf recovery is unavailable, the recommended action will be:\n\n\naction: Destroy the pool and restore from backup.\n\n\nIf this error is encountered during 'zpool import', and if no\nrecovery option is mentioned, the pool is unrecoverable and cannot be\nimported. The pool must be restored from an appropriate backup\nsource. If a recovery option is available, the output from 'zpool\nimport' will look something like the following:\n\n\n# zpool import share\ncannot import 'share': I/O error\n Recovery is possible, but will result in some data loss.\n Returning the pool to its state as of Sun Sep 27 12:31:07 2009\n should correct the problem. Approximately 53 seconds of data\n will have to be discarded, irreversibly. Recovery can be\n attempted by executing 'zpool import -F share'. A scrub of the pool\n is strongly recommended following a successful recovery.\n\n\nRecovery actions are requested with the -F option to either\n'zpool clear' or 'zpool import'. Recovery will result in some data\nloss, because it reverts the pool to an earlier state. A dry-run\nrecovery check can be performed by adding the -n option, affirming if\nrecovery is possible without actually reverting the pool to its\nearlier state.\n" 154 msgstr "\nRun 'zpool status -x' to determine which pool is damaged:\n\n\n# zpool status -x\n pool: test\n state: ONLINE\nstatus: One or more devices has experienced an error and no valid replicas\n are available. Some filesystem data is corrupt, and applications\n may have been affected.\naction: Destroy the pool and restore from backup.\n see: http://illumos.org/msg/ZFS-8000-8A\n scrub: none requested\nconfig:\n\n NAME STATE READ WRITE CKSUM\n test ONLINE 0 0 2\n c0t0d0 ONLINE 0 0 2\n c0t0d1 ONLINE 0 0 0\n\nerrors: 1 data errors, use '-v' for a list\n\n\nUnfortunately, the data cannot be repaired, and the only choice to\nrepair the data is to restore the pool from backup. Applications attempting to\naccess the corrupted data will get an error (EIO), and data may be permanently\nlost.\n\nOn recent versions of Solaris, the list of affected files can be\nretrieved by using the '-v' option to 'zpool status':\n\n\n# zpool status -xv\n pool: test\n state: ONLINE\nstatus: One or more devices has experienced an error and no valid replicas\n are available. Some filesystem data is corrupt, and applications\n may have been affected.\naction: Destroy the pool and restore from backup [all...] |
/titanic_52/usr/src/cmd/geniconvtbl/ |
H A D | yacc.sed | 26 s;\("syntax error - cannot backup"\);gettext(\1);g
|
/titanic_52/usr/src/cmd/backup/restore/ |
H A D | Makefile | 5 # cmd/backup/restore/Makefile 11 # CAUTION: FSTYPE must be defined before including ../Makefile.backup, 23 include ../Makefile.backup
|
/titanic_52/usr/src/cmd/backup/lib/ |
H A D | Makefile | 28 # Has to be before include of Makefile.backup 35 # Include library definitions, then backup definitions, as in general 39 include ../Makefile.backup
|
/titanic_52/usr/src/cmd/svc/milestone/ |
H A D | manifest-import | 399 backup=`echo "$#/$#" | sed 's/.//g'` 422 echo "$backup\c" > /dev/msglog
|
/titanic_52/usr/src/cmd/ |
H A D | Makefile | 76 backup \ 531 backup \
|
/titanic_52/usr/src/lib/libexacct/common/ |
H A D | exacct_ops.c | 323 off_t backup; in ea_next_object() local 356 backup = sizeof (ea_catalog_t); in ea_next_object() 378 backup += sizeof (ea_size_t); in ea_next_object() 407 if (fseeko(f->ef_fp, -backup, SEEK_CUR) == -1) { in ea_next_object()
|
/titanic_52/usr/src/cmd/backup/dump/ |
H A D | Makefile | 5 # cmd/backup/dump/Makefile 28 # CAUTION: FSTYPE must be defined before including ../Makefile.backup, 34 include ../Makefile.backup
|
/titanic_52/usr/src/cmd/sendmail/src/ |
H A D | parseaddr.c | 1132 goto backup; 1139 goto backup; 1151 goto backup; 1175 goto backup; 1226 goto backup; 1237 goto backup; 1246 backup:
|
/titanic_52/usr/src/pkg/manifests/ |
H A D | developer-object-file.mf | 129 license usr/src/cmd/backup/dump/THIRDPARTYLICENSE \ 130 license=usr/src/cmd/backup/dump/THIRDPARTYLICENSE
|
/titanic_52/usr/src/cmd/sgs/packages/common/ |
H A D | postinstall | 120 # backup all existing SGStools.
|
/titanic_52/usr/src/cmd/sgs/lex/common/ |
H A D | ncform | 195 if(yyextra[*yyfnd]){ /* must backup */
|
/titanic_52/usr/src/cmd/boot/bootadm/ |
H A D | bootadm.c | 4336 bam_error(_("failed to create backup for GRUB menu: %s\n"), in synchronize_BE_menu() 4340 BAM_DPRINTF(("%s: successfully created backup GRUB menu: %s\n", in synchronize_BE_menu() 4349 bam_error(_("error propagating backup GRUB menu: %s\n"), in synchronize_BE_menu() 4353 BAM_DPRINTF(("%s: successfully propagated backup GRUB menu: %s\n", in synchronize_BE_menu() 5668 char backup[PATH_MAX]; local 5677 * Look at the backup 5679 (void) snprintf(backup, sizeof (backup), "%s%s", 5682 bfp = fopen(backup, "r"); 5687 backup, strerro 7171 char backup[PATH_MAX]; global() local [all...] |