Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!haven.umd.edu!darwin.sura.net!howland.reston.ans.net!xlink.net!math.fu-berlin.de!informatik.tu-muenchen.de!wiserner From: wiserner@Informatik.TU-Muenchen.DE (Bernd Wiserner) Subject: [BUG?] newfs with bsize = 16 kb ? Sender: news@Informatik.TU-Muenchen.DE (USENET Newssystem) Organization: Technische Universitaet Muenchen, Germany Date: Sat, 23 Oct 1993 19:35:11 GMT Message-ID: <1993Oct23.193511.18122@Informatik.TU-Muenchen.DE> Lines: 23 Hi all, today I tried to create a new fs on my second disk. Because I wanted to optimize the write performance I increased the bsize-field in my disklabel first to 8 kb and then to 16kb . With 8 kb everything was Ok. but then I tried to make a newfs -o0 -l1 -r4500 /dev/sd1e on the disk ( bsize was 16 kb ). First the machine told me that some block couldn't be allocated ( some error wtfs?! ) then I tried to call newfs again: Error: newfs : bad magic number. file `which newfs` told me : /sbin/newfs : data?!. Ok. I tried to build another newfs. gcc hung.Then I realized that my filesystem has gone. I booted the floppy and tried to repair it. My whole /var blew up and another ~200 files. GLUG.No fsck on floppy... mount the unchecked root partition and fsck with fsck from within it. Worked great. Only 10 files lost ... Has this happened to anyone else? Is it a known bug? I used fsck regularly every 2-3 times I booted.I never had an error so far. The disk never had errors,so I think it is because of the newfs command. ( Of course I haven't tried it once again , I don't want to stay another 3 hours befor my box and hoping that my work isn't gone ) Configuration: 486DX 50 , 16 Mb Ram,SCSI adaptec,Disk 0 Dec DSP 1 GB, disk1 Fuji 495 Mb. MfG B.Wiserner