Displaying 5 results from an estimated 5 matches for "ad6s1d".
2010 May 01
5
Single-disk pool corrupted after controller failure
...g: 11420324
pool_guid: 6157028625215863355
hostid: 2563111091
hostname: ''''
top_guid: 1987270273092463401
guid: 1987270273092463401
vdev_tree:
type: ''disk''
id: 0
guid: 1987270273092463401
path: ''/dev/ad6s1d''
whole_disk: 0
metaslab_array: 23
metaslab_shift: 32
ashift: 9
asize: 497955373056
is_log: 0
DTL: 111
--------------------------------------------
LABEL 3
--------------------------------------------
version: 14
name: '...
2008 Aug 02
3
7-STABLE, gjournal and fsck.
...13:43 matrix kernel: GEOM_JOURNAL: Journal 4059706613:
ad4s1g contains data.
Aug 2 19:13:43 matrix kernel: GEOM_JOURNAL: Journal 4059706613:
ad4s1g contains journal.
Aug 2 19:13:43 matrix kernel: GEOM_JOURNAL: Journal ad4s1g clean.
Aug 2 19:13:43 matrix kernel: GEOM_JOURNAL: Journal 188084099: ad6s1d
contains data.
Aug 2 19:13:43 matrix kernel: GEOM_JOURNAL: Journal 188084099: ad6s1d
contains journal.
Aug 2 19:13:43 matrix kernel: GEOM_JOURNAL: Journal ad6s1d clean.
Aug 2 19:13:43 matrix kernel: GEOM_JOURNAL: Journal 2559963968:
ad6s1e contains data.
Aug 2 19:13:43 matrix kernel: GEOM_JO...
2008 Feb 17
6
How to take down a system to the point of requiring a newfs with one line of C (userland)
One line summary:
Too many files in a top-level UFS-2 filesystem directory will cause
a panic on mount.
Kern/Critical/High Priority/SW-Bug
Which FreeBSD Release You Are Using:
6.3-STABLE
Environment (output of "uname -a" on the problem machine):
FreeBSD wahoo.sd67dfl.org 6.3-STABLE FreeBSD 6.3-STABLE #0: Sun Feb
10 21:13:39 CST 2008
2008 Feb 17
6
How to take down a system to the point of requiring a newfs with one line of C (userland)
One line summary:
Too many files in a top-level UFS-2 filesystem directory will cause
a panic on mount.
Kern/Critical/High Priority/SW-Bug
Which FreeBSD Release You Are Using:
6.3-STABLE
Environment (output of "uname -a" on the problem machine):
FreeBSD wahoo.sd67dfl.org 6.3-STABLE FreeBSD 6.3-STABLE #0: Sun Feb
10 21:13:39 CST 2008
2008 Sep 21
3
UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck MANUALLY
Sep 21 08:57:54 belle fsck: /dev/ad4s1d: 1 DUP I=190
Sep 21 08:57:54 belle fsck: /dev/ad4s1d: UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck MANUALLY.
Ok, so I ran fsck manually (even with -y), but yet it refuses to clear/fix
whatever to the questions posed as fsck runs. What does this all mean?
Thanks,
-Clint
--
This message has been scanned for viruses and
dangerous content by MailScanner,