From owner-freebsd-questions@FreeBSD.ORG Sat Oct 23 09:20:53 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2736916A4CE for ; Sat, 23 Oct 2004 09:20:53 +0000 (GMT) Received: from smtp2.dnainternet.net (smtp2.dnainternet.net [62.240.72.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id D01EB43D1D for ; Sat, 23 Oct 2004 09:20:52 +0000 (GMT) (envelope-from erik.u@dnainternet.net) Received: from b-204-211.cable.kpy.customers.dnainternet.fi ([212.149.204.211]:55702smtp2.dnainternet.net with ESMTP id S1228820AbUJWJUw (ORCPT ); Sat, 23 Oct 2004 12:20:52 +0300 Message-ID: <417A2273.6000008@dnainternet.net> Date: Sat, 23 Oct 2004 12:20:51 +0300 From: Erik Udo User-Agent: Mozilla Thunderbird 0.8 (X11/20041012) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: SV: SV: Vinum, and poweroutage... HELP! X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Oct 2004 09:20:53 -0000 Try fsck -y /dev/ad0s1? first, i think that should fix it. Ofcourse you dont need to make it write anything on the disk, just see what fsck want's to do. Thomas Rasmussen wrote: >Do you know why fsck are not able to scan the disk? It seems iam not the >first with this prob... > >And should a -b 32 fix the prob? > > > > > >Med venlig hilsen/Best regards >Thomas Rasmussuen >Network manager, NM Net ApS >Email: tr@nmnet.dk >Tlf./Phone: +45 8677 0606 Fax: +45 8677 0615 > >-----Oprindelig meddelelse----- >Fra: Erik Udo [mailto:erik.u@dnainternet.net] >Sendt: 23. oktober 2004 11:12 >Til: Thomas Rasmussen >Emne: Re: SV: Vinum, and poweroutage... HELP! > >I dont think CLEAR will remove any files, it would say something like: >REMOVE? y/n >If it needed to remove files. Anyway, run fsck -y first so that it does >not >write anything, and you'll see if it wants to remove anything. > >Thomas Rasmussen wrote: > > > >>Because i dont know if it will remove the data... ( don't have backup >>so... ) >> >>There is about 10000 files.. so it will take long time but what to do? >> >>Med venlig hilsen/Best regards >>Thomas Rasmussuen >>Network manager, NM Net ApS >>Email: tr@nmnet.dk >>Tlf./Phone: +45 8677 0606 Fax: +45 8677 0615 >> >>-----Oprindelig meddelelse----- >>Fra: Erik Udo [mailto:erik.u@dnainternet.net] >>Sendt: 23. oktober 2004 11:03 >>Til: Thomas Rasmussen >>Emne: Re: Vinum, and poweroutage... HELP! >> >>Why didn't you answer "yes" to fsck? I dont think it would have removed >>anything... >> >>Few keywords you might want to check: >>scan_ffs >>fsck_ffs >> >>Thomas Rasmussen wrote: >> >> >> >> >> >>>Have a vinum setup... two disk... >>> >>>Vinum.conf >>> >>>drive d1 device /dev/ad2s1e >>>drive d2 device /dev/ad3s1e >>> volume mirror >>> plex org concat >>> sd length 190000m drive d1 >>> plex org concat >>> sd length 190000m drive d2 >>> >>> >>> >>> >>>when I try to run fsck /dev/vinum/mirror >>> >>>it outputs.. >>> >>>BAD SUPER BLOCK: VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST >>>ALTERNATE >>>CANNOT FIGURE OUT FILE SYSTEM PARTITION >>> >>>So I try to run >>> >>>fsck -b 32 -n /dev/vinum/mirror >>> >>>and get a lot of these erros... any? >>>Should a run fsck -b 32 /dev/vinum/mirror and say yes? >>> >>> >>>PARTIALLY ALLOCATED INODE I=1838571 >>>CLEAR? no >>> >>>PARTIALLY ALLOCATED INODE I=1838572 >>>CLEAR? no >>> >>>PARTIALLY ALLOCATED INODE I=1838573 >>>CLEAR? no >>> >>>PARTIALLY ALLOCATED INODE I=1838574 >>>CLEAR? no >>> >>>PARTIALLY ALLOCATED INODE I=1838575 >>>CLEAR? no >>> >>>PARTIALLY ALLOCATED INODE I=1838576 >>>CLEAR? no >>> >>>PARTIALLY ALLOCATED INODE I=1838577 >>>CLEAR? no >>> >>>PARTIALLY ALLOCATED INODE I=1838578 >>>CLEAR? no >>> >>>PARTIALLY ALLOCATED INODE I=1838579 >>>CLEAR? no >>> >>>UNKNOWN FILE TYPE I=1838580 >>>CLEAR? no >>> >>>PARTIALLY ALLOCATED INODE I=1838581 >>>CLEAR? no >>> >>>PARTIALLY ALLOCATED INODE I=1838582 >>>CLEAR? no >>> >>>PARTIALLY ALLOCATED INODE I=1838583 >>>CLEAR? no >>> >>>PARTIALLY ALLOCATED INODE I=1838584 >>>CLEAR? no >>> >>>PARTIALLY ALLOCATED INODE I=1838585 >>>CLEAR? no >>> >>>PARTIALLY ALLOCATED INODE I=1838586 >>>CLEAR? no >>> >>>PARTIALLY ALLOCATED INODE I=1838587 >>>CLEAR? no >>> >>>PARTIALLY ALLOCATED INODE I=1838588 >>>CLEAR? no >>> >>>PARTIALLY ALLOCATED INODE I=1838589 >>>CLEAR? no >>> >>>PARTIALLY ALLOCATED INODE I=1838590 >>>CLEAR? no >>> >>>PARTIALLY ALLOCATED INODE I=1838591 >>>CLEAR? no >>> >>>PARTIALLY ALLOCATED INODE I=1839040 >>>CLEAR? no >>> >>>PARTIALLY ALLOCATED INODE I=1839041 >>>CLEAR? no >>> >>>PARTIALLY ALLOCATED INODE I=1839042 >>> >>> >>> >>> >>>Med venlig hilsen/Best regards >>>Thomas Rasmussuen >>>Network manager, NM Net ApS >>>Email: tr@nmnet.dk >>>Tlf./Phone: +45 8677 0606 Fax: +45 8677 0615 >>> >>> >>>_______________________________________________ >>>freebsd-questions@freebsd.org mailing list >>>http://lists.freebsd.org/mailman/listinfo/freebsd-questions >>>To unsubscribe, send any mail to >>> >>> >>> >>> >>"freebsd-questions-unsubscribe@freebsd.org" >> >> >> >> >>> >>> >>> >>> >> >>_______________________________________________ >>freebsd-questions@freebsd.org mailing list >>http://lists.freebsd.org/mailman/listinfo/freebsd-questions >>To unsubscribe, send any mail to >> >> >"freebsd-questions-unsubscribe@freebsd.org" > > >> >> >> >> > > > >_______________________________________________ >freebsd-questions@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-questions >To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > > >