crash on writing usbstick
Ian Lepore
ian at freebsd.org
Thu Mar 5 22:53:34 UTC 2015
On Thu, 2015-03-05 at 15:34 -0500, Brett Wynkoop wrote:
> On Thu, 05 Mar 2015 07:55:01 -0700
> Ian Lepore <ian at freebsd.org> wrote:
>
> > I spent some time yesterday trying to reproduce this, and couldn't.
> > The only usb thumb drive I have handy right now is 4gb, which isn't
> > quite big enough to hold the entire ports tree, but using your tar|tar
> > incantation it will run to the point where the destination filesystem
> > is full without any errors; I did that twice.
> >
> > You didn't say what you were using as a source for the copy (sdcard,
> > nfs, etc). I was using an nfs mount as source, which on BBB means
> > that usb is involved as both the source and destination.
> >
> > Hmm, I just realized the ports tree I'm copying includes .svn, no
> > wonder it's so big. I'll bet if I exclude that from the copy it'll
> > run to completion.
>
> Greeting-
>
> Would you like access to my BB via ssh and also access to it's console
> via ssh?
>
> I have had the same results with several usb sticks, but all of them
> have been at least 16GB. I am also swapping to the current USB stick
> on a swap partation, but I have had the same results on this stick and
> others without swapping to it.
>
> /usr/ports is on the root fs on the sd card.
>
I got my ports tree onto sdcard then copied it to the usb stick using
the tar|tar command, still can't reproduce the problem at all. Nobody
else has reported any beaglebone IO-related panics or errors for months
either. I wonder what's different about your setup?
(Nice side effect... doing the nfs->usb copy created hundreds of
spurious interrupt messages, I've never been able to reproduce them
reliably before. I think I've got them fixed now; tests still running.)
-- Ian
More information about the freebsd-arm
mailing list