Return to BSD News archive
Xref: sserve comp.os.386bsd.bugs:2254 comp.os.386bsd.questions:10689 Path: sserve!newshost.anu.edu.au!munnari.oz.au!spool.mu.edu!howland.reston.ans.net!EU.net!uknet!demon!awfulhak.demon.co.uk!awfulhak!brian From: brian@awfulhak.demon.co.uk (Brian Somers) Newsgroups: comp.os.386bsd.bugs,comp.os.386bsd.questions Subject: Re: isofs problem or cd problem? Date: 4 Jun 94 04:34:20 Organization: Coverform Ltd. Lines: 31 Message-ID: <BRIAN.94Jun4043420@awfulhak.demon.co.uk> References: <2sje4t$ql0@qualcomm.com> NNTP-Posting-Host: awfulhak.demon.co.uk In-reply-to: bri@qualcomm.com's message of 1 Jun 1994 19:54:37 -0600 In article <2sje4t$ql0@qualcomm.com> bri@qualcomm.com (Brian Ellis) writes: I just received the new FreeBSD 1.1 cdrom and have noticed a serious problem. Is it mine or the cd's? when trying to access *some* files, I get the following behavior: zellis> cd /mnt/filesys/usr/src/sys/i386/isa zellis> file ft.c ft.c: file: read failed (Invalid argument). and in the syslog: cd0: illegal request I've noticed that files with large inode numbers (>200000) exhibit the problem. other files (with small inode numbers) do not have the problem. I have a NetBSD 0.9 system and a toshiba scsi cdrom drive. I've mounted the cdrom using both the "a" and "d" partitions with identical results. -brian Hmm, I've been getting a few segmentation faults from `file'. I havn't yet looked into it, but it's repeatable. -- Brian <brian@awfulhak.demon.co.uk> Don't _EVER_ lose your sense of humour....