crash on writing usbstick

[Brett Wynkoop]

On Sun, 1 Mar 2015 16:55:59 -0700
Warner Losh <imp at bsdimp.com> wrote:

> Your filesystem looks messed up. Panics are likely to haunt you.
> You’ll need to newfs it and reload the data.
> 
> Also, it would be great if you could type ‘tr’ to the db> prompt to
> get a call stack traceback. That would be quite helpful.
> 
> Warner

It seems counter to the design of the ffs, especially with softupdates
enabled that one should have to newfs.  fsck claimed to have fixed the
filesystem, but to be complete I have just done a newfs on the
partation again and will attempt the copy yet again.

root at beaglebone:~ # newfs -J -U /dev/gpt/bbexport
/dev/gpt/bbexport: 14755.0MB (30218160 sectors) block size 32768,
fragment size 4096 using 24 cylinder groups of 626.09MB, 20035 blks,
80256 inodes. with soft updates
super-block backups (for fsck_ffs -b #) at:
 192, 1282432, 2564672, 3846912, 5129152, 6411392, 7693632, 8975872,
10258112, 11540352, 12822592, 14104832, 15387072, 16669312, 17951552,
19233792, 20516032, 21798272, 23080512, 24362752, 25644992, 26927232,
28209472, 29491712 root at beaglebone:~ # 

When it next crashes I will get a backtrace for the team.

-Brett

-- 

wynkoop at wynn.com               http://prd4.wynn.com/wynkoop/pgp-keys.txt
917-642-6925

The Second Amendment extends, prima facie, to all instruments that 
constitute bearable arms, even those that were not in existence 
at the time of the founding. ~ Justice Scalia