© 1995-2013 by The FreeBSD Project. All rights reserved.URL: http://lists.de.freebsd.org
> moooment, jetzt bin ich leicht verwirrt:
> ich verstehe nicht, warum die stripesets (tmp, data2), die auch auf ad0 liegen,
> wo fsck die fehler meldet, augenscheinlich FUNKTIONIEREN.
Nun habe ich kurzerhand ad0s1a mit newfs formatieren lassen, dies, und nun auch fsck machen keine Fehler.
Nun blicke ich langsam wieder durch.
Da das rootfs auf ad4s1a liegt musste ich am loader-prompt die Stelle angeben
boot: ad(4,a)/kernel
Jetzt kommen auch keine "invalid systemcall" - etc - errors am sh-promt. Vermutlich wurde zuvor von der defekten ad0s1a gebootet. Das dies in der Vergangenheit funktionierte und auf einmal nichtmehr wird dann wohl doch am neuen world oder so gelegen haben.
die aktuellen vinum-Ausgaben über die serielle console lauten:
vinum: loaded
vinum: reading configuration from /dev/ad6s1e
vinum: updating configuration from /dev/ad3s1e
vinum: updating configuration from /dev/ad4s1e
vinum: updating configuration from /dev/ad0s1e
vinum: /dev is mounted read-only, not rebuilding /dev/vinum
Warning: defective objects
P alcajail.p0 C State: flaky Subdisks: 1 Size: 5120 MB
P alcajail.p1 C State: flaky Subdisks: 1 Size: 5120 MB
P alcausr.p0 C State: flaky Subdisks: 1 Size: 17 GB
P alcausr.p1 C State: flaky Subdisks: 1 Size: 17 GB
P alcadata1.p0 C State: flaky Subdisks: 1 Size: 49 GB
P alcadata1.p1 C State: flaky Subdisks: 1 Size: 49 GB
S alcajail.p0.s0 State: reborn PO: 0 B Size: 5120 MB
S alcajail.p1.s0 State: reborn PO: 0 B Size: 5120 MB
S alcausr.p0.s0 State: reborn PO: 0 B Size: 17 GB
S alcausr.p1.s0 State: reborn PO: 0 B Size: 17 GB
S alcadata1.p0.s0 State: reborn PO: 0 B Size: 49 GB
S alcadata1.p1.s0 State: reborn PO: 0 B Size: 49 GB
swapon: adding /dev/ad6s1b as swap device
swapon: adding /dev/ad4s1b as swap device
swapon: adding /dev/ad0s1b as swap device
Automatic boot in progress...
/dev/ad4s1a: FILESYSTEM CLEAN; SKIPPING CHECKS
/dev/ad4s1a: clean, 51515 free (379 frags, 6392 blocks, 0.5% fragmentation)
/dev/ad6s1a: FILESYSTEM CLEAN; SKIPPING CHECKS
/dev/ad6s1a: clean, 57334 free (238 frags, 7137 blocks, 0.3% fragmentation)
/dev/vinum/alcausr: CANNOT READ: BLK 16
/dev/vinum/alcausr: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
/dev/vinum/alcajail: CANNOT READ: BLK 16
/dev/vinum/alcajail: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
/dev/vinum/alcadata1: CANNOT READ: BLK 16
/dev/vinum/alcadata1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
/dev/vinum/alcatmp: FILESYSTEM CLEAN; SKIPPING CHECKS
/dev/vinum/alcatmp: clean, 1011859 free (51 frags, 126476 blocks, 0.0% fragmentation)
/dev/vinum/alcavar: BAD SUPER BLOCK: MAGIC NUMBER WRONG
/dev/vinum/alcavar: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
/dev/vinum/alcavar: /dev/vinum/alcadata2: FILESYSTEM CLEAN; SKIPPING CHECKS
/dev/vinum/alcadata2: clean, 94172442 free (18 frags, 11771553 blocks, 0.0% fragmentation)
THE FOLLOWING FILE SYSTEMS HAD AN UNEXPECTED INCONSISTENCY:
/dev/vinum/alcausr (/usr), /dev/vinum/alcajail (/jail), /dev/vinum/alcadata1 (/vol/alcadata1), /dev/vinum/alcavar (/var)
Automatic file system check failed . . . help!
Enter full pathname of shell or RETURN for /bin/sh:
# vinum
vinum -> l -r
4 drives:
D alca80gb3 State: up Device /dev/ad0s1e Avail: 0/76330 MB (0%)
S alcatmp.p0.s0 State: up PO: 0 B Size: 512 MB
S alcadata2.p0.s0 State: up PO: 0 B Size: 74 GB
D alca20gb1 State: up Device /dev/ad3s1e Avail: 0/19574 MB (0%)
S alcatmp.p0.s1 State: up PO: 512 MB Size: 512 MB
S alcadata2.p0.s1 State: up PO: 74 GB Size: 18 GB
D alca80gb1 State: up Device /dev/ad4s1e Avail: 0/76330 MB (0%)
S alcavar.p0.s0 State: up PO: 0 B Size: 3072 MB
S alcajail.p0.s0 State: reborn PO: 0 B Size: 5120 MB
S alcausr.p0.s0 State: reborn PO: 0 B Size: 17 GB
S alcadata1.p0.s0 State: reborn PO: 0 B Size: 49 GB
D alca80gb2 State: up Device /dev/ad6s1e Avail: 0/76330 MB (0%)
S alcavar.p1.s0 State: up PO: 0 B Size: 3072 MB
S alcajail.p1.s0 State: reborn PO: 0 B Size: 5120 MB
S alcausr.p1.s0 State: reborn PO: 0 B Size: 17 GB
S alcadata1.p1.s0 State: reborn PO: 0 B Size: 49 GB
6 volumes:
V alcavar State: up Plexes: 2 Size: 3072 MB
P alcavar.p0 C State: up Subdisks: 1 Size: 3072 MB
P alcavar.p1 C State: up Subdisks: 1 Size: 3072 MB
S alcavar.p0.s0 State: up PO: 0 B Size: 3072 MB
S alcavar.p1.s0 State: up PO: 0 B Size: 3072 MB
V alcajail State: up Plexes: 2 Size: 5120 MB
P alcajail.p0 C State: flaky Subdisks: 1 Size: 5120 MB
P alcajail.p1 C State: flaky Subdisks: 1 Size: 5120 MB
S alcajail.p0.s0 State: reborn PO: 0 B Size: 5120 MB
S alcajail.p1.s0 State: reborn PO: 0 B Size: 5120 MB
V alcausr State: up Plexes: 2 Size: 17 GB
P alcausr.p0 C State: flaky Subdisks: 1 Size: 17 GB
P alcausr.p1 C State: flaky Subdisks: 1 Size: 17 GB
S alcausr.p0.s0 State: reborn PO: 0 B Size: 17 GB
S alcausr.p1.s0 State: reborn PO: 0 B Size: 17 GB
V alcadata1 State: up Plexes: 2 Size: 49 GB
P alcadata1.p0 C State: flaky Subdisks: 1 Size: 49 GB
P alcadata1.p1 C State: flaky Subdisks: 1 Size: 49 GB
S alcadata1.p0.s0 State: reborn PO: 0 B Size: 49 GB
S alcadata1.p1.s0 State: reborn PO: 0 B Size: 49 GB
V alcatmp State: up Plexes: 1 Size: 1024 MB
P alcatmp.p0 C State: up Subdisks: 2 Size: 1024 MB
S alcatmp.p0.s0 State: up PO: 0 B Size: 512 MB
S alcatmp.p0.s1 State: up PO: 512 MB Size: 512 MB
V alcadata2 State: up Plexes: 1 Size: 92 GB
P alcadata2.p0 C State: up Subdisks: 2 Size: 92 GB
S alcadata2.p0.s0 State: up PO: 0 B Size: 74 GB
S alcadata2.p0.s1 State: up PO: 74 GB Size: 18 GB
10 plexes:
P alcavar.p0 C State: up Subdisks: 1 Size: 3072 MB
S alcavar.p0.s0 State: up PO: 0 B Size: 3072 MB
P alcavar.p1 C State: up Subdisks: 1 Size: 3072 MB
S alcavar.p1.s0 State: up PO: 0 B Size: 3072 MB
P alcajail.p0 C State: flaky Subdisks: 1 Size: 5120 MB
S alcajail.p0.s0 State: reborn PO: 0 B Size: 5120 MB
P alcajail.p1 C State: flaky Subdisks: 1 Size: 5120 MB
S alcajail.p1.s0 State: reborn PO: 0 B Size: 5120 MB
P alcausr.p0 C State: flaky Subdisks: 1 Size: 17 GB
S alcausr.p0.s0 State: reborn PO: 0 B Size: 17 GB
P alcausr.p1 C State: flaky Subdisks: 1 Size: 17 GB
S alcausr.p1.s0 State: reborn PO: 0 B Size: 17 GB
P alcadata1.p0 C State: flaky Subdisks: 1 Size: 49 GB
S alcadata1.p0.s0 State: reborn PO: 0 B Size: 49 GB
P alcadata1.p1 C State: flaky Subdisks: 1 Size: 49 GB
S alcadata1.p1.s0 State: reborn PO: 0 B Size: 49 GB
P alcatmp.p0 C State: up Subdisks: 2 Size: 1024 MB
S alcatmp.p0.s0 State: up PO: 0 B Size: 512 MB
S alcatmp.p0.s1 State: up PO: 512 MB Size: 512 MB
P alcadata2.p0 C State: up Subdisks: 2 Size: 92 GB
S alcadata2.p0.s0 State: up PO: 0 B Size: 74 GB
S alcadata2.p0.s1 State: up PO: 74 GB Size: 18 GB
12 subdisks:
S alcavar.p0.s0 State: up PO: 0 B Size: 3072 MB
D alca80gb1 State: up Device /dev/ad4s1e Avail: 0/76330 MB (0%)
S alcavar.p1.s0 State: up PO: 0 B Size: 3072 MB
D alca80gb2 State: up Device /dev/ad6s1e Avail: 0/76330 MB (0%)
S alcajail.p0.s0 State: reborn PO: 0 B Size: 5120 MB
D alca80gb1 State: up Device /dev/ad4s1e Avail: 0/76330 MB (0%)
S alcajail.p1.s0 State: reborn PO: 0 B Size: 5120 MB
D alca80gb2 State: up Device /dev/ad6s1e Avail: 0/76330 MB (0%)
S alcausr.p0.s0 State: reborn PO: 0 B Size: 17 GB
D alca80gb1 State: up Device /dev/ad4s1e Avail: 0/76330 MB (0%)
S alcausr.p1.s0 State: reborn PO: 0 B Size: 17 GB
D alca80gb2 State: up Device /dev/ad6s1e Avail: 0/76330 MB (0%)
S alcadata1.p0.s0 State: reborn PO: 0 B Size: 49 GB
D alca80gb1 State: up Device /dev/ad4s1e Avail: 0/76330 MB (0%)
S alcadata1.p1.s0 State: reborn PO: 0 B Size: 49 GB
D alca80gb2 State: up Device /dev/ad6s1e Avail: 0/76330 MB (0%)
S alcatmp.p0.s0 State: up PO: 0 B Size: 512 MB
D alca80gb3 State: up Device /dev/ad0s1e Avail: 0/76330 MB (0%)
S alcatmp.p0.s1 State: up PO: 512 MB Size: 512 MB
D alca20gb1 State: up Device /dev/ad3s1e Avail: 0/19574 MB (0%)
S alcadata2.p0.s0 State: up PO: 0 B Size: 74 GB
D alca80gb3 State: up Device /dev/ad0s1e Avail: 0/76330 MB (0%)
S alcadata2.p0.s1 State: up PO: 74 GB Size: 18 GB
D alca20gb1 State: up Device /dev/ad3s1e Avail: 0/19574 MB (0%)
vinum ->
Wie ist nun den flaky / reborn-Stats beizukommen?
Vielen Dank im Voraus.
Grüße,
Oskar
__________________________________________________________________________
Die sicherste Form der Kommunikation: E-Mails verschluesseln, Spam-Filter,
Adressverifizierung, digitale Unterschrift: http://freemail.web.de
To Unsubscribe: send mail to majordomo.FreeBSD.org
with "unsubscribe de-bsd-questions" in the body of the message
Received on Mon 18 Aug 2003 - 15:53:15 CEST