Date: Sun, 1 Mar 2015 18:48:52 -0700 From: Warner Losh <imp@bsdimp.com> To: Brett Wynkoop <freebsd-arm@wynn.com> Cc: freebsd-arm@freebsd.org Subject: Re: crash on writing usbstick Message-ID: <F79FBD40-6002-4C38-A191-A74A88DA929B@bsdimp.com> In-Reply-To: <20150301203244.55578413@ivory.wynn.com> References: <20150301041855.5352663e@ivory.wynn.com> <20150301144653.63b38cdf@ivory.wynn.com> <20150301184456.7b5e6487@ivory.wynn.com> <1DC8221F-64EA-418C-8CE5-5FFA4F3DBC64@bsdimp.com> <20150301203244.55578413@ivory.wynn.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] > On Mar 1, 2015, at 6:32 PM, Brett Wynkoop <freebsd-arm@wynn.com> wrote: > > On Sun, 1 Mar 2015 16:55:59 -0700 > Warner Losh <imp@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@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@beaglebone:~ # > > When it next crashes I will get a backtrace for the team. I agree you shouldn’t have to do this. However, this will reset things to a known state, which is important with testing. If you screwed something up in a prior version that’s unusual, fsck might not fix it. Since we started seeing weird FS junk, we need to make sure that we have a good state. This will let us tell the difference between a FS that’s weird because it didn’t get flushed on the first panic, and a FS that’s weird because we’re bogusly writing weird stuff to it. Warner [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJU88GFAAoJEGwc0Sh9sBEAwzYQAJVR4L1vI7OPYA3Cy/kX5zYp Xmz2S3NBekTXJ3Cq03k3VqGa8BzA6IEA2Pe5OqiPHL5uXngPcvhJytRH16YfpctV GMar69NooE/NcJO8/InMFhKTQMnbz720tLCqMr15Zx7DVlkt8VqUUiwkhHIGMbbz 6dL2Tm9pouv5qytXX+58K3JbcdrrwQrUdWD2YaFYpp09zUrDlXArcxZ2uu2RYdql w79au/QtzqXQtvJ/0QLFAxH7RreEnoXlxLIZCZbqwNqvXzfe3VNj2UuRLlcpuAlk ///lEd7vrtehl0sHaVpvNGtXPeDtDl7+6KWPpXRbOx2ORAenBXQIS9opWY5pFGDP bMxDVvBepKb6SiOq1tMIo6V7mO9SSvEN9U9bFKh6iy6KYKag8BPXkzNkR5FbS9rV QPKd/9fxM45Ubi0aGH9GUox+XHiJh42PuVYLPKHMQzt7Uvw7giu1ceR6IvR+NfG9 Ri8ZXxBN+7uWjHtnGcyACF7cDij7qkJVAEW4nohJMR1/Usy16HO+mZRtrMAi6MCM gm02XxIgRmPo0eCrUX3cg/9R9LsTwkwvaG4vOB+vSC3Ap5WjvEyHwuKpK80bO+Cl xsH4D8zH5Aq15WuY66dM27RxZ3thI5L2e0kZBNE2OiENiL6gfJTrAliIS7q8jDcM 41V7wv9WLfmg7xe9cl5e =SNc8 -----END PGP SIGNATURE-----help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F79FBD40-6002-4C38-A191-A74A88DA929B>