Re: dumping large partition to USB drive fails
On Mon, Jun 25, 2007 at 10:45:07PM -0400, Yoshihiro Ota wrote: > It's probabry your disk is dying based on your output. > > I've being using GELI for while, i.e. like a year, with dump/resotre, > too. I never had problems with dump/restore. > > My disk also failed recently with very similer messages. > The weird thing is, when I use the USB disk without encryption, it works fine. So, dumping a non-encrypted partition to an encrypted disk works. As does dumping from an encrypted partition to a non-encrypted disk. Only in the case of where both are encrypted it fails. I tried testing the USB disk with smartctl, but it failed with a SCSI command error. :-( Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgphn7Qog39vQ.pgp Description: PGP signature
Re: dumping large partition to USB drive fails
It's probabry your disk is dying based on your output. I've being using GELI for while, i.e. like a year, with dump/resotre, too. I never had problems with dump/restore. My disk also failed recently with very similer messages. Hiro On Mon, 25 Jun 2007 19:40:45 +0200 Roland Smith <[EMAIL PROTECTED]> wrote: > Some background; > > I'm using a 160GB USB harddisk to write dumps to. This disk is encrypted > with GEOM_ELI; > > umass0: Prolific Technology Inc. Mass Storage Device, rev 2.00/1.00, addr 2 > da0 at umass-sim0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-0 device > da0: 40.000MB/s transfers > da0: 238475MB (488397168 512 byte sectors: 255H 63S/T 30401C) > GEOM_ELI: Device da0.eli created. > GEOM_ELI: Encryption: AES-CBC 256 > GEOM_ELI: Crypto: software > > > Since I've converted my largest partition (/home) to GEOM_ELI as well, > I'm having trouble making backups. > > slackbox:~$ df -h > Filesystem SizeUsed Avail Capacity Mounted on > /dev/ar0s1a496M 88M368M19%/ > devfs 1.0K1.0K 0B 100%/dev > /dev/ar0s1g.eli120G 65G 46G59%/home > /dev/ar0s1e496M 24K456M 0%/tmp > /dev/ar0s1f 19G4.5G 13G25%/usr > /dev/ar0s1d1.9G147M1.6G 8%/var > /dev/da0.eli 226G100G107G48%/mnt/root > > > Backing up non-encrypted partitions like /, /usr and /var works > fine. But when I get to /home, the following happens; > > (da0:umass-sim0:0:0:0): AutoSense Failed > GEOM_ELI: Crypto WRITE request failed (error=5). > da0.eli[WRITE(offset=1165967687 > 68, length=131072)] > GEOM_ELI: Crypto WRITE request failed (error=5). > da0.eli[WRITE(offset=1165968998 > 40, length=131072)] > GEOM_ELI: Crypto WRITE request failed (error=5). > da0.eli[WRITE(offset=1165970309 > 12, length=131072)] > GEOM_ELI: Crypto WRITE request failed (error=5). > da0.eli[WRITE(offset=1165971619 > 84, length=131072)] > GEOM_ELI: Crypto WRITE request failed (error=5). > da0.eli[WRITE(offset=1165972930 > 56, length=131072)] > GEOM_ELI: Crypto WRITE request failed (error=5). > da0.eli[WRITE(offset=1165974241 > 28, length=131072)] > GEOM_ELI: Crypto WRITE request failed (error=5). > da0.eli[WRITE(offset=1165975552 > 00, length=131072)] > GEOM_ELI: Crypto WRITE request failed (error=5). > da0.eli[WRITE(offset=1165976862 > 72, length=131072)] > GEOM_ELI: Crypto WRITE request failed (error=5). > da0.eli[WRITE(offset=1165966376 > 96, length=131072)] > g_vfs_done():da0.eli[WRITE(offset=116596768768, length=131072)]error = 5 > g_vfs_done():da0.eli[WRITE(offset=116596899840, length=131072)]error = 5 > g_vfs_done():da0.eli[WRITE(offset=116597030912, length=131072)]error = 5 > g_vfs_done():da0.eli[WRITE(offset=116597161984, length=131072)]error = 5 > g_vfs_done():da0.eli[WRITE(offset=116597293056, length=131072)]error = 5 > g_vfs_done():da0.eli[WRITE(offset=116597424128, length=131072)]error = 5 > g_vfs_done():da0.eli[WRITE(offset=116597555200, length=131072)]error = 5 > g_vfs_done():da0.eli[WRITE(offset=116597686272, length=131072)]error = 5 > g_vfs_done():da0.eli[WRITE(offset=116596637696, length=131072)]error = 5 > GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=65536, > len > gth=2048)] > GEOM_ELI: Crypto WRITE request failed (error=5). > da0.eli[WRITE(offset=6144000, l > ength=16384)] > GEOM_ELI: Crypto WRITE request failed (error=5). > da0.eli[WRITE(offset=6160384, l > ength=6144)] > GEOM_ELI: Crypto WRITE request failed (error=5). > da0.eli[WRITE(offset=1161638707 > 20, length=16384)] > GEOM_ELI: Crypto WRITE request failed (error=5). > da0.eli[WRITE(offset=1163565137 > 92, length=16384)] > GEOM_ELI: Crypto WRITE request failed (error=5). > da0.eli[WRITE(offset=1165491568 > 64, length=16384)] > GEOM_ELI: Crypto WRITE request failed (error=5). > da0.eli[WRITE(offset=1165979484 > 16, length=131072)] > GEOM_ELI: Crypto WRITE request failed (error=5). > da0.eli[WRITE(offset=1165980794 > 88, length=131072)] > GEOM_ELI: Crypto WRITE request failed (error=5). > da0.eli[WRITE(offset=1165982105 > 60, length=131072)] > GEOM_ELI: Crypto WRITE request failed (error=5). > da0.eli[WRITE(offset=1165983416 > 32, length=131072)] > GEOM_ELI: Crypto WRITE request failed (error=5). > da0.eli[WRITE(offset=1165984727 > 04, length=131072)] > GEOM_ELI: Crypto WRITE request failed (error=5). > da0.eli[WRITE(offset=1165984727 > 04, length=131072)] > GEOM_ELI: Crypto WRITE request failed (error=5). > da0.eli[WRITE(offset=1165986037 > 76, length=131072)] > GEOM_ELI: Crypto WRITE request failed (error=5). > da0.eli[WRITE(offset=1165987348 > 48, length=131072)] > GEOM_ELI: Crypto WRITE request failed (error=5). > da0.eli[WRITE(offset=1165988659 > 20, length=131072)] > GEOM_ELI: Crypto WRITE request failed (error=5). > da0.eli[WRITE(offset=1165978173 > 44, length=131072)] > g_vfs_done():da0.eli[WRITE(offset=65536, length=2048)]error = 5 > g_vfs_done():
acpi_smbus_read_2: AE_ERROR on mac pro
I have -STABLE (amd64) running on an 8-way Mac Pro system. It's all working great except I get the following message on the console every couple of seconds. acpi_smbus_read_2: AE_ERROR 0x10 I've (google...) found one comment about Freebsd and the Mac Pro that includes this message in it's dmesg output but doesn't actually mention it. It doesn't seem to be causing any problems but I'd just as soon fix whatever it's whining about. Is there some central site for freebsd on intel mac's? Is this error familiar to anyone? g. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: PXE booting issues
Morgan, I had much better luck using PXELINUX to chain-load FreeBSD. I wrote up an article on the subject (http://web.irtnog.org/doc/how-to/freebsd-install-pxe-wds), but the corresponding blog entry might make for a shorter read (http://web.irtnog.org/~xenophon/blog/archive/2007/04/22/struggling-to -boot-freebsd-from-pxelinux). Obviously, you aren't using WDS or RIS, but the principle is the same. Best wishes, Matthew -- "Rogues are very keen in their profession, and know already much more than we can teach them respecting their several kinds of roguery." - A. C. Hobbs in _Locks and Safes_ (1853) smime.p7s Description: S/MIME cryptographic signature
dumping large partition to USB drive fails
Some background; I'm using a 160GB USB harddisk to write dumps to. This disk is encrypted with GEOM_ELI; umass0: Prolific Technology Inc. Mass Storage Device, rev 2.00/1.00, addr 2 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 238475MB (488397168 512 byte sectors: 255H 63S/T 30401C) GEOM_ELI: Device da0.eli created. GEOM_ELI: Encryption: AES-CBC 256 GEOM_ELI: Crypto: software Since I've converted my largest partition (/home) to GEOM_ELI as well, I'm having trouble making backups. slackbox:~$ df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/ar0s1a496M 88M368M19%/ devfs 1.0K1.0K 0B 100%/dev /dev/ar0s1g.eli120G 65G 46G59%/home /dev/ar0s1e496M 24K456M 0%/tmp /dev/ar0s1f 19G4.5G 13G25%/usr /dev/ar0s1d1.9G147M1.6G 8%/var /dev/da0.eli 226G100G107G48%/mnt/root Backing up non-encrypted partitions like /, /usr and /var works fine. But when I get to /home, the following happens; (da0:umass-sim0:0:0:0): AutoSense Failed GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=1165967687 68, length=131072)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=1165968998 40, length=131072)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=1165970309 12, length=131072)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=1165971619 84, length=131072)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=1165972930 56, length=131072)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=1165974241 28, length=131072)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=1165975552 00, length=131072)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=1165976862 72, length=131072)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=1165966376 96, length=131072)] g_vfs_done():da0.eli[WRITE(offset=116596768768, length=131072)]error = 5 g_vfs_done():da0.eli[WRITE(offset=116596899840, length=131072)]error = 5 g_vfs_done():da0.eli[WRITE(offset=116597030912, length=131072)]error = 5 g_vfs_done():da0.eli[WRITE(offset=116597161984, length=131072)]error = 5 g_vfs_done():da0.eli[WRITE(offset=116597293056, length=131072)]error = 5 g_vfs_done():da0.eli[WRITE(offset=116597424128, length=131072)]error = 5 g_vfs_done():da0.eli[WRITE(offset=116597555200, length=131072)]error = 5 g_vfs_done():da0.eli[WRITE(offset=116597686272, length=131072)]error = 5 g_vfs_done():da0.eli[WRITE(offset=116596637696, length=131072)]error = 5 GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=65536, len gth=2048)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=6144000, l ength=16384)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=6160384, l ength=6144)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=1161638707 20, length=16384)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=1163565137 92, length=16384)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=1165491568 64, length=16384)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=1165979484 16, length=131072)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=1165980794 88, length=131072)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=1165982105 60, length=131072)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=1165983416 32, length=131072)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=1165984727 04, length=131072)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=1165984727 04, length=131072)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=1165986037 76, length=131072)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=1165987348 48, length=131072)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=1165988659 20, length=131072)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=1165978173 44, length=131072)] g_vfs_done():da0.eli[WRITE(offset=65536, length=2048)]error = 5 g_vfs_done():da0.eli[WRITE(offset=6144000, length=16384)]error = 5 g_vfs_done():da0.eli[WRITE(offset=6160384, length=6144)]error = 5 g_vfs_done():da0.eli[WRITE(offset=116163870720, length=16384)]error = 5 g_vfs_done():da0.eli[WRITE(offset=116356513792, length=16384)]error = 5 g_vfs_done():da0.eli[WRITE(offset=116549156864, length=16384)]error = 5 g_vfs_done():da0.eli[WRITE(offset=116597948416, length=131072)]error = 5 g_vfs_done():da0.eli[WRITE(offset=116598079488, length=131072)]error = 5 g_vfs_done():da0.eli[WRITE(offset=116598210560, length=131072)]error = 5 g_vfs_done():da0.eli[W
MP-Safe quotas for RELENG_6
Hello, I backported the MP-Safe quotas patch for RELENG_6. Besides what the title said, it includes several fixes for quotas operation. I would commit the patch based on the users feedback, assuming the re@ would not object. Please, test it. http://people.freebsd.org/~kib/quotagiant/quotas-RELENG_6-20070623-1455.patch Draft version of commit message: MFC: part of rev. 1.412 of sys/kern/vfs_syscalls.c: Remove explicit calls to lock and unlock Giant and replace them with VFS_LOCK_GIANT/VFS_UNLOCK_GIANT calls. MFC this for quotactl only. rev. 1.433 of sys/kern/vfs_syscalls.c: Busy filesystem around call of VFS_QUOTACTL() vfs op. rev. 1.289 of sys/ufs/ufs/ufs_vnops.c: Remove unneeded getinoquota() call in the ufs_access(). rev. 1.83 of sys/ufs/ufs/ufs_lookup.c: Call getinoquota() before allocating new block for the directory to properly account for block allocation. rev. 1.30 of sys/ufs/ufs/quota.h rev. 1.327 of sys/ufs/ffs/ffs_vfsops.c rev. 1.93 of sys/ufs/ufs/ufs_quota.c: Implement fine-grained locking for UFS quotas. rev. 1.205 of sys/ufs/ffs/ffs_softdep.c rev. 1.328 of sys/ufs/ffs/ffs_vfsops.c: Mark UFS as being MP-Safe in "options QUOTA" case too. Remove no more neccessary Giant acquisions in softdepend processing code. rev. 1.206 of sys/ufs/ffs/ffs_softdep.c: Revert rev. 1.205. Replace unconditional acquision of Giant when QUOTAS are defined with VFS_LOCK_GIANT(NULL) call. rev. 1.211 of sys/ufs/ffs/ffs_softdep.c rev. 1.69 of sys/ufs/ufs/ufs_inode.c: Fix livelock that could occur when snapshoting UFS with quotas, where some quota limit was exceeded. pgpbCOWnIJB6A.pgp Description: PGP signature
Re: miniBSD vs 6.2-STABLE
Morgan Reed wrote: > I now have my target PXE booting from my FreeBSD host (chalk one up to > not writing config files at ungodly hours of the night, thanks to > Danny for spotting the error.) > > The boot is proceeding to the boot menu but after this the kernel freezes; > With acpi.ko in the image the acpi module loads, the next spinner > appears and the system freezes. > Without acpi.ko I get the message "ACPI autoload failed - no such file > or directory", the next spinner appears and the system freezes. > > My kernel is a stripped GENERIC, essentially minus a bunch of network > drivers (the driver for the adapter in the machine is still there ;o) > ), and all the SCSI controllers. > Is this embedded system booting with a standard monitor and keyboard attached, or via serial console? What you are seeing seems to remind me of a system that is configured to display boot output via video when there is no monitor connection (from my own MiniBSD work with the Soekris NET4501 and PCEngines WRAP platforms). -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
miniBSD vs 6.2-STABLE
I now have my target PXE booting from my FreeBSD host (chalk one up to not writing config files at ungodly hours of the night, thanks to Danny for spotting the error.) The boot is proceeding to the boot menu but after this the kernel freezes; With acpi.ko in the image the acpi module loads, the next spinner appears and the system freezes. Without acpi.ko I get the message "ACPI autoload failed - no such file or directory", the next spinner appears and the system freezes. My kernel is a stripped GENERIC, essentially minus a bunch of network drivers (the driver for the adapter in the machine is still there ;o) ), and all the SCSI controllers. Any suggestions would be greatly appreciated. Morgan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
