Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!newshost.marcam.com!news.mathworks.com!panix!ddsw1!not-for-mail From: mikebo@MCS.COM (Michael Borowiec) Newsgroups: comp.os.386bsd.questions Subject: FBSD 2.0R - Tape install prob & 1.x/2.0 UFS compatibility Date: 2 Dec 1994 00:53:45 -0600 Organization: MCSnet, Chicago Area Public Internet Access Lines: 78 Message-ID: <3bmg9p$clp@Mars.mcs.com> NNTP-Posting-Host: mars.mcs.com The FreeBSD 2.0 SCSI tape load is not working on my system. I am currently running FreeBSD 1.1.5.1 on the system in question, so I don't believe my setup is causing the failure. The 2.0 kernel output at boot time indicates the tape drive IS seen. I elect to install bindist first and select tape install. I am prompted to "mount" the tape, which I do, and a window pops up labelled something like "Tape extract results" and the thing just sits there staring at me. The tape drive is never accessed. Although I did notice the SCSI bus activity light flicker briefly, there is no tape motion. After a few minutes of nothing, I elect to abort the installation. Does the load expect the tape at a specific SCSI ID? If so, I didn't see it in the docs. I am running an Adaptec 1542B with several disks and an Archive Viper QIC150 at SCSI ID 2. Some additional points... Nowhere in the docs or install program does it describe the load tape FORMAT required by 2.0. I ASSUMED it was the same as 1.1.5.1, so I created a TAR tape with ALL the tarballs on it (bindist, compat1x_tgz, dict, games, manpages, etc.). Is this right? If so, it is just dumb luck. A neophyte user would not have had a clue how to build an install tape. If I missed this in the docs, could you tell me where it is? Someone claimed it was in a file called RELNOTES-FreeBSD, but I don't find that file in 2.0-RELEASE anywhere, and the snippet that was posted didn't address the isue of multiple distributions on the same tape (I want everything on one tape). All I have is RELNOTES which doesn't say squat about the load tape format. Regarding 1.x/2.0 UFS filesystem compatibility: In some article or another, Garrett A. Wollman wrote: > The clean bit processing in 2.0 will result in fsck complaining about > your superblock. However, you can safely ignore this error, because > the 1.1.5 kernel doesn't notice it. By contrast, the lack of clean > bit processing in 1.1.5 will cause the 2.0 fsck to complain. It complains about more than the clean bit... Having read that filesystems now have 64-bit offsets, I was curious if 2.0 can fsck and mount 1.1.5.1 partitions. After my load failure, I fsck'ed one of the newly created 2.0 partitions with 1.1.5.1 fsck and found a load of corruption. (DIRECTORY CORRUPTED, MISSING '.', etc.) But what COMPLETELY blew me away was reading the following... > The above only applies to 4.2-compatible (``version 1'') FFS > filesystems, such as those originally newfs'ed by FreeBSD 1.x and not > later converted. If you have a ``version 2'' FFS filesystem, such as > is the default under FreeBSD 2.0, while the kernel will be able to > read it just fine (except for symbolic links which have changed in > format between the versions), fsck will be unable to make any sense > out of it. > > >If it is a no-no, how do I convert my 5 disks from one to the other? > > fsck -c2 /dev/device # convert to version 2 > fsck -c1 /dev/device # convert to version 1 - untested > > However, this is an extremely invasive operation, and we don't take > any responsibility for fsck screwing up your data in the process. AAAAAAAAAARGH!!! Symlinks are broke between versions?! I have to backup, newfs and restore? I've got gigabytes of stuff on 1.1.5.1 partitions! Dare I trust dump/restore, tar or whatever between versions? Don't get me wrong... I admire you guys for putting a LOAD of TLC into this release. I just wish the release notes had prep'ed me on install and filesystem issues. Did someone put an incorrect release notes file in the 2.0-RELEASE directory, or what? - Mike -- -------------------------------------------------------------------------- Michael Borowiec All tied to their things, mikebo@MCS.COM they are netted by the strings... Free to flutter, in memory of their wasted wings... P.Gabriel