Re: very silent, but heavy filesystem-crash
Hi, ... thanks for your assistance. I On Fri, Jan 28, 2000 at 08:22:32AM -0800, Rodney W. Grimes wrote: Next step is run the ``save'' fsck: fsck -n /scratch /someplacewithspace 21 there is some illuminated filesystem-hacker who would like to take a peek. (I would allow ssh-access to the box ...) $1.00/MB for me to recover it ... I was used to this kind of service for hosed FAT-filesystems and hosed partition tables ;) ... (I did it by stuffing the 'hosed disks' into one of my unix-boxes and working on the raw devices ...) if you need it. ... fortunately not. Just have a look at the mountpoint's name I don't do it for fun. ... understandable :), I made the offer just for the case anybody wants to track down a potential bug. But as it comes out I had (in fact :( ) a typo in the disklabel. I checked the disklabel two times before my post to -current, but I had obviously a little problem with my 'eye-brain-interlink'. I really shouldn't admit this in this forum, should I? ... But in relabeling the disk I left the disklabel as follows: #size offsetfstype [fsize bsize bps/cpg] b: 10485760 swap# (Cyl.0 - 65*) c: 179124120unused0 0 # (Cyl.0 - 1114*) g: 1791241204.2BSD 1024 819216 # (Cyl.0 - 1114*) Sorry for bothering all of you, feeling soo stultified and the big and heavy hat (with a certain pattern on it) weighs on my head ... Thanks, Andreas -- : Anti-Spam Petition: http://www.politik-digital.de/spam/: : PGP-Key:http://www.tse-online.de/~ab/public-key: : Key fingerprint: 12 13 EF BC 22 DD F4 B6 3C 25 C9 06 DC D3 45 9B : To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: very silent, but heavy filesystem-crash
:But as it comes out I had (in fact :( ) a typo in the disklabel. : :I checked the disklabel two times before my post to -current, but :I had obviously a little problem with my 'eye-brain-interlink'. : :I really shouldn't admit this in this forum, should I? ... But :in relabeling the disk I left the disklabel as follows: : :#size offsetfstype [fsize bsize bps/cpg] : b: 10485760 swap# (Cyl.0 - 65*) : c: 179124120unused0 0 # (Cyl.0 - 1114*) : g: 1791241204.2BSD 1024 819216 # (Cyl.0 - 1114*) : : :Sorry for bothering all of you, feeling soo stultified :and the big and heavy hat (with a certain pattern on it) weighs :on my head ... : : :Thanks, :Andreas Heh! Don't feel bad, the only reason I thought it was a disklabel problem is because I've done the same thing myself in the past, with similar results! What we really need to do is fix disklabel to at least warn of overlaps. The only reason I don't make the same mistakes these days is because every time I run the beast I check my calculations 6 ways from sunday, forwards and backwards. -Matt Matthew Dillon [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: very silent, but heavy filesystem-crash
... Starting an 'fsck' results in: cage:[/] # fsck /scratch ** /dev/da1s1g ** Last Mounted on /scratch ** Phase 1 - Check Blocks and Sizes PARTIALLY TRUNCATED INODE I=16 SALVAGE? [yn] ^C * FILE SYSTEM MARKED DIRTY * Next step is run the ``save'' fsck: fsck -n /scratch /someplacewithspace 21 Then take a look at the logfile and see just how many more errors it would have found had you let it procede... I interrupted the fsck-run as soon as I decided that it might be advisable to leave it in its hosed state just for the case that there is some illuminated filesystem-hacker who would like to take a peek. (I would allow ssh-access to the box ...) $1.00/MB for me to recover it if you need it. I don't do it for fun. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: very silent, but heavy filesystem-crash
:Hi there, : : I reported a former heavy filesystem crash recently; have a look : at: : :http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=846852+849687+/usr/local/www/db/text/2000/freebsd-current/2123.freebsd-current : : I got it again. : Meanwhile my system got updated to : FreeBSD abc.xyz.de 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Sat Jan 22 11:17:16 CET 2000 : : The system is complete soft-updates free. : : This time I had no jailed processes running; the machine was idle : most of the time during the last few days and was rebooted (cleanly), : yesterday. : : The (now totally hosed) file-system was mounted thru the following : fstab-entry: : :/dev/da1s1g /scratch ufs rw 2 2 :Bye, :Andreas :Andreas Braukmann - private site - cat /etc/fstab disklabel da1s1 (so it prints out the label) There's a good chance you overlapped a partition. -Matt Matthew Dillon [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
