Home
last modified time | relevance | path

Searched full:destroyed (Results 1 – 25 of 1045) sorted by relevance

12345678910>>...42

/freebsd/tests/sys/cddl/zfs/tests/cli_root/zpool_import/
H A Dzpool_import_destroyed_001_neg.ksh35 # A destroyed pool cannot be imported, even if an out-of-date non-destroyed
39 # destroyed the pool, reinserted the spare disk, and then tried to import the
40 # pool. Since the pool was destroyed, nothing should've happened. But the
41 # spare disk had a non-destroyed label, so zpool tried to import it. A panic
47 # 3) The pool gets destroyed
58 # Destroy the pool, so DISK1's and DISK2's labels will be in the destroyed
59 # state, leaving DISK0's label as the most recent non-destroyed label
H A Dzpool_import_destroyed_002_neg.ksh35 # "zpool import" will not show destroyed pools, even if out-of-date
36 # non-destroyed label is present
40 # 2) The pool gets destroyed
48 # Destroy the pool, so DISK1's and DISK2's labels will be in the destroyed
49 # state, leaving DISK0's label as the most recent non-destroyed label
55 log_fail "ERROR: Destroyed pool visible"
H A Dzpool_import_test.sh55 atf_set "descr" "Destroyed pools are not listed unless with -D option is specified."
80 …atf_set "descr" "Destroyed pools devices was moved to another directory,it still can be imported c…
105 atf_set "descr" "Destroyed pools devices was renamed, it still can be importedcorrectly."
130 …atf_set "descr" "For mirror, N-1 destroyed pools devices was removed or usedby other pool, it stil…
155 …atf_set "descr" "For raidz, one destroyed pools devices was removed or used byother pool, it still…
180 …atf_set "descr" "For raidz2, two destroyed pools devices was removed or used byother pool, it stil…
255 …atf_set "descr" "For strip pool, any destroyed pool devices was demaged,zpool import -D will faile…
320 atf_set "descr" "'zpool import' can import destroyed disk-backed pools"
521 …atf_set "descr" "'zpool import' will not show destroyed pools, even if an out-of-date non-destroye…
542 …atf_set "descr" "'zpool import' will not show destroyed pools, even if an out-of-date non-destroye…
H A Dzpool_import_011_neg.ksh36 # For strip pool, any destroyed pool devices was demaged, zpool import -D
43 # 4. Verify 'import -D' pool A will failed whenever pool B was destroyed
64 # Recreate virtual devices to avoid destroyed pool information on files.
70 log_assert "For strip pool, any destroyed pool devices was demaged," \
/freebsd/contrib/llvm-project/lldb/source/Target/
H A DThreadPlan.cpp192 s->PutCString("Null thread plan - thread has been destroyed."); in GetDescription()
198 "error: %s called on thread that has been destroyed (tid = 0x%" PRIx64 in ValidatePlan()
204 log->Error("%s called on thread that has been destroyed (tid = 0x%" PRIx64 in ValidatePlan()
214 "error: %s called on thread that has been destroyed (tid = 0x%" PRIx64 in ShouldStop()
220 log->Error("%s called on thread that has been destroyed (tid = 0x%" PRIx64 in ShouldStop()
230 "error: %s called on thread that has been destroyed (tid = 0x%" PRIx64 in WillStop()
236 log->Error("%s called on thread that has been destroyed (tid = 0x%" PRIx64 in WillStop()
246 "error: %s called on thread that has been destroyed (tid = 0x%" PRIx64 in DoPlanExplainsStop()
252 log->Error("%s called on thread that has been destroyed (tid = 0x%" PRIx64 in DoPlanExplainsStop()
264 "error: %s called on thread that has been destroyed (tid = 0x%" PRIx64 in MischiefManaged()
[all …]
/freebsd/sys/contrib/openzfs/tests/zfs-tests/tests/functional/cli_root/zfs_destroy/
H A Dzfs_destroy_010_pos.ksh36 # defer-destroyed, make sure that the 'zfs destroy -R' works as expected.
38 # kernel will automatically remove the defer-destroyed snapshot when the
39 # clone is destroyed.
45 # 5. Verify that the snapshot and clone are destroyed.
63 log_assert "'zfs destroy -R' works on deferred destroyed snapshots"
78 log_pass "'zfs destroy -R' works on deferred destroyed snapshots"
H A Dzfs_destroy_012_pos.ksh24 # Deferred destroyed snapshots remain until the last hold is released.
32 # 6. Verify that the snapshot is destroyed.
61 log_assert "deferred destroyed snapshots remain until last hold is released"
76 log_pass "deferred destroyed snapshots remain until last hold is released"
H A Dzfs_destroy_clone_livelist.ksh26 # destroyed
31 # destroyed
170 log_pass "Clone with the livelist feature enabled could be destroyed," \
171 "also could be promoted and destroyed as expected."
H A Dzfs_destroy_016_pos.ksh57 log_fail "zfs destroy should not have destroyed" \
60 log_fail "zfs destroy should not have destroyed" \
66 log_fail "zfs destroy should have destroyed" \
69 log_fail "zfs destroy should have destroyed" \
/freebsd/share/man/man9/
H A Dg_wither_geom.940 is to be destroyed.
44 detached and destroyed automatically.
46 the provider will be destroyed.
48 destroyed.
59 function gives no guarantee that the geom will be immediately destroyed, mostly
/freebsd/sys/contrib/openzfs/tests/zfs-tests/tests/functional/nestedfs/
H A Dnestedfs_001_pos.ksh41 # a mounted file system cannot be destroyed.
46 # 3. Show a nested file system with file systems cannot be destroyed
51 log_assert "Verify a nested file system can be created/destroyed."
57 "cannot be destroyed."
/freebsd/contrib/llvm-project/clang/lib/StaticAnalyzer/Checkers/
H A DPthreadLockChecker.cpp35 Destroyed, enumerator
48 static LockState getDestroyed() { return LockState(Destroyed); } in getDestroyed()
60 bool isDestroyed() const { return K == Destroyed; } in isDestroyed()
274 CheckNames[CheckKind], "Use destroyed lock", "Lock checker"}); in initBugType()
307 // When a lock is destroyed, in some semantics(like PthreadSemantics) we are not
309 // the 'possibly destroyed' state. There is a short time frame for the
311 // destroyed. Before we model the next operation over that lock, we call this
313 // - either to destroyed state or back to its previous state.
316 // successfully destroyed and it returns a non-zero value otherwise.
321 // Existence in Destroyed also ensures that the lock state for lockR is either in resolvePossiblyDestroyedMutex()
[all …]
/freebsd/sys/contrib/openzfs/tests/zfs-tests/tests/functional/cli_root/zpool_import/
H A Dzpool_import_011_neg.ksh38 # For strip pool, any destroyed pool devices was demaged, zpool import -D
45 # 4. Verify 'import -D' pool A will failed whenever pool B was destroyed
57 # Recreate virtual devices to avoid destroyed pool information on files.
63 log_assert "For strip pool, any destroyed pool devices was demaged," \
H A Dzpool_import_003_pos.ksh38 # Destroyed pools are not listed unless with -D option is specified.
56 log_assert "Destroyed pools are not listed unless with -D option is specified."
68 log_pass "Destroyed pool only can be listed with -D option."
/freebsd/tests/sys/cddl/zfs/tests/nestedfs/
H A Dnestedfs_001_pos.ksh39 # a mounted file system cannot be destroyed.
44 # 3. Show a nested file system with file systems cannot be destroyed
63 log_assert "Verify a nested file system can be created/destroyed."
71 "cannot be destroyed."
/freebsd/sys/contrib/openzfs/man/man8/
H A Dzpool-import.887 Destroyed pools, pools that were previously destroyed with the
114 Lists destroyed pools only.
131 Destroyed pools, pools that were previously destroyed with the
160 Imports destroyed pools only.
308 Imports destroyed pool.
H A Dzfs-rollback.851 In order to do so, all intermediate snapshots and bookmarks must be destroyed by
59 Only direct snapshots of the specified filesystem are destroyed by either of
70 option to force an unmount of any clone file systems that are to be destroyed.
/freebsd/contrib/llvm-project/llvm/include/llvm/IR/
H A DLegacyPassManager.h12 // destroyed when the PassManager is destroyed.
44 /// the Pass to the PassManager. When the PassManager is destroyed, the pass
45 /// will be destroyed as well, so there is no need to delete the pass. This
/freebsd/sys/contrib/openzfs/man/man7/
H A Dzpool-features.7332 are destroyed.
414 The feature becomes inactive when all BRT ZAPs are destroyed.
434 state when all v2 bookmarks are destroyed.
448 state when all bookmarks with these fields are destroyed.
601 state when all datasets that use this feature are destroyed.
625 state when all datasets that use this feature are destroyed.
714 are destroyed.
729 are destroyed.
742 state when all datasets that ever had a large micro ZAP are destroyed.
758 until all clones have been destroyed.
[all …]
/freebsd/share/man/man4/
H A Dnvmf.439 command and destroyed via the
85 peripherals are destroyed after the first failed I/O request.
86 Note that any destroyed
/freebsd/sys/contrib/openzfs/tests/zfs-tests/tests/functional/rootpool/
H A Drootpool_003_neg.ksh38 # system related filesystems can not be renamed or destroyed
51 log_assert "system related filesystems can not be renamed or destroyed"
62 log_pass "system related filesystems can not be renamed or destroyed"
/freebsd/contrib/llvm-project/llvm/tools/llvm-cov/
H A DRenderingSupport.h18 /// when destroyed.
32 // color when destroyed. in ColoredRawOstream()
48 /// is true. Returns an object that resets the color when destroyed.
/freebsd/sys/contrib/openzfs/tests/zfs-tests/tests/functional/cli_root/zfs_clone/
H A Dzfs_clone_deeply_nested.ksh26 # Deeply nested clones can be created and destroyed successfully
43 log_assert "Deeply nested clones should be created and destroyed without issues"
70 log_pass "Deeply nested clones can be created and destroyed successfully"
/freebsd/crypto/krb5/src/man/
H A Dkdestroy.man45 credentials cache is destroyed.
52 collection to be destroyed.
75 your .logout file, so that your tickets are destroyed automatically
/freebsd/crypto/krb5/src/windows/leash/htmlhelp/html/
H A DKDESTROY.htm36 destroyed.
58 in your <I>.logout</I> file, so that your tickets are destroyed automatically
98 Only the tickets in the specified credentials cache are destroyed.
100 changing tickets. These should probably be destroyed too, or all of a

12345678910>>...42