Just a follow-up with some more information:
I now doubt that the problem that I reported in the original
message is the drive dying: I've just done some read tests (cat
largefile /dev/null) on the other USB2-attached drive (also a
Western Digital MyBook, but this one is a USB2+Firewire one with
Oliver Lehmann wrote:
tunefs -L usr mirror/gm0s1f.journal
tunefs -L files da0p1.journal
/dev/ufs and /dev/label contained all the given label. Then I rebooted
once more - again into the single user mode.
Now ufs/files and ufs/usr is gone so glabel in conjunction
The additional information I have (over the PR) is that:
1) Files over 64K cause the problem, not just larger files
I thought it was over 1 MB or so. But maybe I'm wrong. ISTR that I
couldn't trigger it with some images of around 70K.
I discovered it originally with a 72K file. After some
That is: it seems to work fine for some fraction of a minute
(doesn't seem to be longer than a minute, anyway), and then
stops completely for several minutes (processes reading or
writing sit in D state in ps) and then starts again, after
logging Request completed with CAM_REQ_CMP_ERR\nRetrying
Hi.
Thanks to one man who provided access to his machine, I seem to found
how to fix device detection on nVidia MCP55 SATA controller on amd64
8.0. Looks like this controller need some time (very short) to enable
BAR(5) memory access after PCI configuration register written. Probably
some changes
hi sirs,
apologized me for disturbing this list but ireally have problem s.
i make my own release by follwoing document in releng articles.
here is my command
cd /usr/src/release
time make CHROOTDIR=/kaitag/KAITAG BUILDNAME=7.2-RELEASE \
CVSROOT=/var/ftp/pub/ncvs
