Re: mount and umount large capacity external USB HDD (fstab)
... snip snip >> >> We will read that recipe. Should anyone make additions to this thread >> we >> are all eyes_&_ears. >> > > As was mentioned before, the limitationcomes from the defintion of the > partition > structures. Firstly the fdisk structure introduced with the IBM PC (I > think) has onlt room for > 32 bits on its sector tables. secondly the bsd 'label' structure > introduced > in the 80s has a similar limitiation. > The new structure to get around this is the GPT structure. you need to > partition > the drive with a gpt capable partitioning tool.. gpart claims to do > this (though > I have never done it as I don't have a need (yet)). This limitiation > will affect > any system which you wil use to write those partition types and is > indepenent > of file system. In addition Once you have made a partition big > enough, you > will need to populate it wirth a filesystem capable of representing > data to that scale. > UFS2 and ZFS are two candidates for this. > > If you take a modern Windows, it will probably partitionthe drive > using a GPT table > or some similar modern structure.(I don't have any modern windows > system so I can't tell > you exactly what they do, but they MUST have done the same thingif > they didn't use GPT itself.) > This is a separate step from puting the file system on, though the > windows tools may > present it as a single step. > > I hope y'all will find this useful. > Thank you. As Mr. Hesser pointed out earlier; it must be time for us to learn gpart and friends :-) ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: mount and umount large capacity external USB HDD (fstab)
I believe there are 2 limits you may be encountering. The disk is larger than 2TiB and is low-level formatted with 4096 bytes sectors. The 2TiB limit results from clculations with 32 bit integers and 512 byte sectors. The large sector size is almost certainly the problem with "dd"...you can read less than a sector, but an attempt to write less than a sector will fail. Try bs=4k. I'm running 8 Stable as of a few days ago. The "fdisk" sources on this system were updated 11/22/2010, but appear to handle sector sizes only up to 2048 bytes. I haven't checked to see if it handles disk or partition sizes above 2TiB, but it doesn't matter, it won't handle your disk properly, and I doubt that the FBSD 7.3 fdisk would either. There is no option for sector size, it's a hard-coded limit which is too small. Bsdlabel may have similar limits. The version on this system was last modified 09/26/2010. It reads the sectorsize from the disk and therefore should have no trouble with a 3tb disk. I don't know whether the 7.3 fdisk has these modifications, but with fdisk failing, it doesn't matter. If you are using the disk only under freebsd you might try using 'bsdlabel' on the entire disk (da0), but check I suspect your bsdlabel may not be upgraded yet (check sbin/bsdlabel). The manual page for 'gpart' claims that it was introduced in 7.0, and I would think it would be working reasonably by 7.3. It should be able to handle large disks and partitions with no trouble, and is much easier to use than the old stuff. You said in your last email that 'gpart show' showed nothing, but that may be because it had nothing intelligible to show. If you haven't tried it yet, and the disk contains no data which you might lose, then try the recipe from the link I gave you. Create a couple of partitions, then try 'gpart show'. Alternately, you may try getting recent versions of fdisk and bsdlabel from cvs or svn, increase the sector size limit in fdisk, and try that route again. -- Duane H. Hesser Thank you all for your input. We must admit, we have a bit more reading to do to fully understand what "Nagilum" was providing. On the other hand, we do understand more of what Mr. Hesser was saying, however, we aren't prepared to upgrade to to 8.x or start playing around by replacing/updating individual utilities on this 'live 7.3 system'. Perhaps on a test machine 'first'. Until then we will have to take the whimp way out and format the 3TB USB device with NTFS and mount it until we are better versed on exactly where Freebsds' support is for these HDD's that are greater than @-TB in size. We really would like at least one (1) FreeBSD machine that is all, dedicated so to speak, BSD. We will read that recipe. Should anyone make additions to this thread we are all eyes_&_ears. As was mentioned before, the limitationcomes from the defintion of the partition structures. Firstly the fdisk structure introduced with the IBM PC (I think) has onlt room for 32 bits on its sector tables. secondly the bsd 'label' structure introduced in the 80s has a similar limitiation. The new structure to get around this is the GPT structure. you need to partition the drive with a gpt capable partitioning tool.. gpart claims to do this (though I have never done it as I don't have a need (yet)). This limitiation will affect any system which you wil use to write those partition types and is indepenent of file system. In addition Once you have made a partition big enough, you will need to populate it wirth a filesystem capable of representing data to that scale. UFS2 and ZFS are two candidates for this. If you take a modern Windows, it will probably partitionthe drive using a GPT table or some similar modern structure.(I don't have any modern windows system so I can't tell you exactly what they do, but they MUST have done the same thingif they didn't use GPT itself.) This is a separate step from puting the file system on, though the windows tools may present it as a single step. I hope y'all will find this useful. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org" ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: mount and umount large capacity external USB HDD (fstab)
> > I believe there are 2 limits you may be encountering. The disk is larger > than 2TiB and is low-level formatted with 4096 bytes sectors. The 2TiB > limit results from clculations with 32 bit integers and 512 byte sectors. > > The large sector size is almost certainly the problem with "dd"...you > can read less than a sector, but an attempt to write less than a sector > will fail. Try bs=4k. > > I'm running 8 Stable as of a few days ago. The "fdisk" sources on > this system were updated 11/22/2010, but appear to handle sector sizes > only > up to 2048 bytes. I haven't checked to see if it handles disk or > partition > sizes above 2TiB, but it doesn't matter, it won't handle your disk > properly, > and I doubt that the FBSD 7.3 fdisk would either. There is no option for > sector size, it's a hard-coded limit which is too small. > > Bsdlabel may have similar limits. The version on this system was last > modified 09/26/2010. It reads the sectorsize from the disk and therefore > should have no trouble with a 3tb disk. I don't know whether the 7.3 > fdisk has these modifications, but with fdisk failing, it doesn't matter. > If you are using the disk only under freebsd you might try using > 'bsdlabel' > on the entire disk (da0), but check I suspect your bsdlabel may not be > upgraded yet (check sbin/bsdlabel). > > The manual page for 'gpart' claims that it was introduced in 7.0, and I > would think it would be working reasonably by 7.3. It should be able > to handle large disks and partitions with no trouble, and is much easier > to use than the old stuff. You said in your last email that 'gpart show' > showed nothing, but that may be because it had nothing intelligible to > show. If you haven't tried it yet, and the disk contains no data which > you might lose, then try the recipe from the link I gave you. Create > a couple of partitions, then try 'gpart show'. > > Alternately, you may try getting recent versions of fdisk and bsdlabel > from cvs or svn, increase the sector size limit in fdisk, and try that > route again. > > -- > Duane H. Hesser > Thank you all for your input. We must admit, we have a bit more reading to do to fully understand what "Nagilum" was providing. On the other hand, we do understand more of what Mr. Hesser was saying, however, we aren't prepared to upgrade to to 8.x or start playing around by replacing/updating individual utilities on this 'live 7.3 system'. Perhaps on a test machine 'first'. Until then we will have to take the whimp way out and format the 3TB USB device with NTFS and mount it until we are better versed on exactly where Freebsds' support is for these HDD's that are greater than @-TB in size. We really would like at least one (1) FreeBSD machine that is all, dedicated so to speak, BSD. We will read that recipe. Should anyone make additions to this thread we are all eyes_&_ears. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: mount and umount large capacity external USB HDD (fstab)
On Mon, 7 Feb 2011 01:21:11 -0500 em...@guice.ath.cx wrote: > I really hope we aren't as ignorant as what these articles are making us > appear to be ... > > We will try and not be long winded on this. > > OUR GOAL: > To add a USB 3TB drive, with a UFS2 fs, to an already running x86 FreeBSD > 7.3-p1 system. > > PROBLEMS __ The following sections from the FBSD Handbook are erroneous > and/or not properly working with this device. > > 18.3.1 Using sysinstall(8) __ After all is said and done, we are only left > with da0s1, da0s2 and da0s3 within /dev. > > 18.3.2 Using Command Line Utilities > 18.3.2.1 Using Slices __ some of the commands in this section do not yield > positive results and fail. Example, as seen in the handbook: > > WORKSTATION# dd if=/dev/zero of=/dev/da0 bs=1k count=1 > dd: /dev/da0: Invalid argument > 1+0 records in > 0+0 records out > 0 bytes transferred in 0.000108 secs (0 bytes/sec) > > When we edit the __bs=1k__ to __bs=512k__ this appears to complete > successfully. Another example: > > WORKSTATION# fdisk -BI da0 > *** Working on device /dev/da0 *** > fdisk: /boot/mbr: length must be a multiple of sector size > > Honestly, how does this stuff make it in to the handbook? Lets look at a > final example from the handbook; how is a novice suppose to know what to > do in the resulting file after using the following command, > > bsdlabel -e da0s1 > > The system we are working on/with __ > - > WORKSTATION# uname -r > 7.3-RELEASE-p1 > - > WORKSTATION# df -h > Filesystem SizeUsed Avail Capacity Mounted on > /dev/ad4s1a484M412M 33M93%/ > devfs 1.0K1.0K 0B 100%/dev > /dev/ad4s1f3.4G168K3.2G 0%/tmp > /dev/ad4s1d106G 23G 74G23%/usr > /dev/ad4s1e 29G4.3G 22G16%/var > - > USB DEVICE: (3TB) > da0 at umass-sim0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-4 device > da0: 40.000MB/s transfers > da0: 2861588MB (732566645 4096 byte sectors: 255H 63S/T 45600C) > > > Everyone says read the handbook, then when we do, this is what we get. > I believe there are 2 limits you may be encountering. The disk is larger than 2TiB and is low-level formatted with 4096 bytes sectors. The 2TiB limit results from clculations with 32 bit integers and 512 byte sectors. The large sector size is almost certainly the problem with "dd"...you can read less than a sector, but an attempt to write less than a sector will fail. Try bs=4k. I'm running 8 Stable as of a few days ago. The "fdisk" sources on this system were updated 11/22/2010, but appear to handle sector sizes only up to 2048 bytes. I haven't checked to see if it handles disk or partition sizes above 2TiB, but it doesn't matter, it won't handle your disk properly, and I doubt that the FBSD 7.3 fdisk would either. There is no option for sector size, it's a hard-coded limit which is too small. Bsdlabel may have similar limits. The version on this system was last modified 09/26/2010. It reads the sectorsize from the disk and therefore should have no trouble with a 3tb disk. I don't know whether the 7.3 fdisk has these modifications, but with fdisk failing, it doesn't matter. If you are using the disk only under freebsd you might try using 'bsdlabel' on the entire disk (da0), but check I suspect your bsdlabel may not be upgraded yet (check sbin/bsdlabel). The manual page for 'gpart' claims that it was introduced in 7.0, and I would think it would be working reasonably by 7.3. It should be able to handle large disks and partitions with no trouble, and is much easier to use than the old stuff. You said in your last email that 'gpart show' showed nothing, but that may be because it had nothing intelligible to show. If you haven't tried it yet, and the disk contains no data which you might lose, then try the recipe from the link I gave you. Create a couple of partitions, then try 'gpart show'. Alternately, you may try getting recent versions of fdisk and bsdlabel from cvs or svn, increase the sector size limit in fdisk, and try that route again. -- Duane H. Hesser ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: mount and umount large capacity external USB HDD (fstab)
- Message from em...@guice.ath.cx - Date: Mon, 7 Feb 2011 00:39:08 -0500 From: em...@guice.ath.cx Subject: Re: mount and umount large capacity external USB HDD (fstab) To: duane.hes...@gmail.com Cc: freebsd-usb@freebsd.org Lastly, we don't fully understand, nor have we found an article or man page that explains (in a way we can understand), how to use the 'bs= ' to the 'dd' command. Within the 'man dd' the examples show 'bs=512' however, in the FreeBSD Handbook 18.3.2.1 Using Slices, they demonstrate dd using 'bs=1k'; we continue to be confused. Should we take this confusion to another list? bs is the block size for the transfers. If you want to fill a harddisk you want to use a big blocksize such as bs=1m. When you have a smaller block size dd will be more busy pushing the blocks around which will only increase CPU load and lower your transfer rate. As for the unit following the number: Where sizes are specified, a decimal, octal, or hexadecimal number of bytes is expected. If the number ends with a ``b'', ``k'', ``m'', ``g'', or ``w'', the number is multiplied by 512, 1024 (1K), 1048576 (1M), 1073741824 (1G) or the number of bytes in an integer, respectively. Two or more numbers may be separated by an ``x'' to indicate a product. - End message from em...@guice.ath.cx - #_ __ _ __ http://www.nagilum.org/ \n icq://69646724 # # / |/ /__ _(_) /_ _ nagi...@nagilum.org \n +491776461165 # # // _ `/ _ `/ / / // / ' \ Amiga (68k/PPC): AOS/NetBSD/Linux # # /_/|_/\_,_/\_, /_/_/\_,_/_/_/_/ Mac (PPC): MacOS-X / NetBSD /Linux # # /___/ x86: FreeBSD/Linux/Solaris/Win2k ARM9: EPOC EV6 # cakebox.homeunix.net - all the machine one needs.. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: mount and umount large capacity external USB HDD (fstab)
I really hope we aren't as ignorant as what these articles are making us appear to be ... We will try and not be long winded on this. OUR GOAL: To add a USB 3TB drive, with a UFS2 fs, to an already running x86 FreeBSD 7.3-p1 system. PROBLEMS The following sections from the FBSD Handbook are erroneous and/or not properly working with this device. 18.3.1 Using sysinstall(8) After all is said and done, we are only left with da0s1, da0s2 and da0s3 within /dev. 18.3.2 Using Command Line Utilities 18.3.2.1 Using Slices some of the commands in this section do not yield positive results and fail. Example, as seen in the handbook: WORKSTATION# dd if=/dev/zero of=/dev/da0 bs=1k count=1 dd: /dev/da0: Invalid argument 1+0 records in 0+0 records out 0 bytes transferred in 0.000108 secs (0 bytes/sec) When we edit the bs=1k to bs=512k this appears to complete successfully. Another example: WORKSTATION# fdisk -BI da0 *** Working on device /dev/da0 *** fdisk: /boot/mbr: length must be a multiple of sector size Honestly, how does this stuff make it in to the handbook? Lets look at a final example from the handbook; how is a novice suppose to know what to do in the resulting file after using the following command, bsdlabel -e da0s1 The system we are working on/with - WORKSTATION# uname -r 7.3-RELEASE-p1 - WORKSTATION# df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/ad4s1a484M412M 33M93%/ devfs 1.0K1.0K 0B 100%/dev /dev/ad4s1f3.4G168K3.2G 0%/tmp /dev/ad4s1d106G 23G 74G23%/usr /dev/ad4s1e 29G4.3G 22G16%/var - USB DEVICE: (3TB) da0 at umass-sim0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-4 device da0: 40.000MB/s transfers da0: 2861588MB (732566645 4096 byte sectors: 255H 63S/T 45600C) Everyone says read the handbook, then when we do, this is what we get. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: mount and umount large capacity external USB HDD (fstab)
This is a corrected version of my last post -- typo discovered -- > On Sat, 29 Jan 2011 18:24:42 -0500 > freebsd_u...@guice.ath.cx wrote: >> Hope we are posting to the correct list ... >> We__re using a laptop for our temp mail-server and would like to attach a >> two (2) or three (3) TB external USB HDD for back-up purposes. Would someone be kind enough to point us to a step-by-step article on what needs >> to be entered in the /etc/fstab to allow us to leave the drive connected >> and facilitate auto mount/umount across system reboots; the results Google >> are presenting isn__t sufficient. Perhaps it__s or search terms that aren__t >> on point. >> Thanks. > The following link provides a 'recipe' for using gpart to partition the disk. > http://scratching.psybermonkey.net/2010/06/freebsd-how-to-format-partition.html If you use the '-L' flag to newfs after creating one or more partitions, e.g. > newfs -L "image" daXp1 > This will create a device node in /dev/ufs (/dev/ufs/image). > You may then create fstab entries as usual, but using the label device, e.g. > /dev/ufs/image/usr/image ufs rw > 2 2 > Unless you add "noauto" to the options (rw,noauto) the system will fsck and mount the partition on boot. > You can, of course, create several partitions on the disk, using a separate label (-L) for each. > Is this what you needed? Thank you for your prompt reply. This appears to be what we were looking for, however, the gpart method has opened up another list of speed-bumps (so to speak), meaning, while reading about 'gpart' on our fbsd-7.3-P1 system; the command 'gpart show' yields no results. We have shelved the gpart suggestion and will try and do this with itemized commands from the CLI; something that we have never needed to do in the past --first time for everything. (smile) - Currently our USB drive is seen as: da0 at umass-sim0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-4 device da0: 40.000MB/s transfers da0: 2861588MB (732566645 4096 byte sectors: 255H 63S/T 45600C) we are considering using the following: # dd if=/dev/zero of=/dev/da0 bs=1k count=1 # fdisk -BI da0 #Initialize your new disk # bsdlabel -B -w da0s1 auto #Label it. # bsdlabel -e da0s1 # Edit the bsdlabel just created and add any partitions. # mkdir -p /mnt/drv-e # mkdir -p /mnt/drv-f # mkdir -p /mnt/drv-g # mkdir -p /mnt/drv-h # newfs /dev/da0s1e # Repeat this for every partition you created. # newfs /dev/da0s1f # newfs /dev/da0s1g # newfs /dev/da0s1h # mount /dev/da1s1e /mnt/drv-e # Mount the partition(s) # mount /dev/da1s1f /mnt/drv-f # mount /dev/da1s1g /mnt/drv-g # mount /dev/da1s1h /mnt/drv-h - # vi /etc/fstab # Add the appropriate entry/entries to your /etc/fstab. Is our thinking 'sane' when doing the above? Initial example taken/borrowed from the FreeBSD Handbook 18.3.2.1 Using Slices. - - Lastly, we don't fully understand, nor have we found an article or man page that explains (in a way we can understand), how to use the 'bs= ' to the 'dd' command. Within the 'man dd' the examples show 'bs=512' however, in the FreeBSD Handbook 18.3.2.1 Using Slices, they demonstrate dd using 'bs=1k'; we continue to be confused. Should we take this confusion to another list? Thanks in advance ... ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: mount and umount large capacity external USB HDD (fstab)
> On Sat, 29 Jan 2011 18:24:42 -0500 > freebsd_u...@guice.ath.cx wrote: >> Hope we are posting to the correct list ... >> We__re using a laptop for our temp mail-server and would like to attach a >> two (2) or three (3) TB external USB HDD for back-up purposes. Would someone be kind enough to point us to a step-by-step article on what needs >> to be entered in the /etc/fstab to allow us to leave the drive connected >> and facilitate auto mount/umount across system reboots; the results Google >> are presenting isn__t sufficient. Perhaps it__s or search terms that aren__t >> on point. >> Thanks. > The following link provides a 'recipe' for using gpart to partition the disk. > http://scratching.psybermonkey.net/2010/06/freebsd-how-to-format-partition.html If you use the '-L' flag to newfs after creating one or more partitions, e.g. > newfs -L "image" daXp1 > This will create a device node in /dev/ufs (/dev/ufs/image). > You may then create fstab entries as usual, but using the label device, e.g. > /dev/ufs/image/usr/image ufs rw > 2 2 > Unless you add "noauto" to the options (rw,noauto) the system will fsck and mount the partition on boot. > You can, of course, create several partitions on the disk, using a separate label (-L) for each. > Is this what you needed? Thank you for your prompt reply. This appears to be what we were looking for, however, the gpart method has opened up another list of speed-bumps (so to speak), meaning, while reading about 'gpart' on our fbsd-7.3-P1 system; the command 'gpart show' yields no results. We have shelved the gpart suggestion and will try and do this with itemized commands from the CLI; something that we have never needed to do in the past --first time for everything. (smile) - Currently our USB drive is seen as: da0 at umass-sim0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-4 device da0: 40.000MB/s transfers da0: 2861588MB (732566645 4096 byte sectors: 255H 63S/T 45600C) we are considering using the following: # dd if=/dev/zero of=/dev/da0 bs=1k count=1 # fdisk -BI da0 #Initialize your new disk # bsdlabel -B -w da1s1 auto #Label it. # bsdlabel -e da0s1 # Edit the bsdlabel just created and add any partitions. # mkdir -p /mnt/drv-e # mkdir -p /mnt/drv-f # mkdir -p /mnt/drv-g # mkdir -p /mnt/drv-h # newfs /dev/da0s1e # Repeat this for every partition you created. # newfs /dev/da0s1f # newfs /dev/da0s1g # newfs /dev/da0s1h # mount /dev/da1s1e /mnt/drv-e # Mount the partition(s) # mount /dev/da1s1f /mnt/drv-f # mount /dev/da1s1g /mnt/drv-g # mount /dev/da1s1h /mnt/drv-h - # vi /etc/fstab # Add the appropriate entry/entries to your /etc/fstab. Is our thinking 'sane' when doing the above? Initial example taken/borrowed from the FreeBSD Handbook 18.3.2.1 Using Slices. - - Lastly, we don't fully understand, nor have we found an article or man page that explains (in a way we can understand), how to use the 'bs= ' to the 'dd' command. Within the 'man dd' the examples show 'bs=512' however, in the FreeBSD Handbook 18.3.2.1 Using Slices, they demonstrate dd using 'bs=1k'; we continue to be confused. Should we take this confusion to another list? Thanks in advance ... ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: mount and umount large capacity external USB HDD (fstab)
On Sat, 29 Jan 2011 18:24:42 -0500 freebsd_u...@guice.ath.cx wrote: > Hope we are posting to the correct list ... > > We__re using a laptop for our temp mail-server and would like to attach a > two (2) or three (3) TB external USB HDD for back-up purposes. Would > someone be kind enough to point us to a step-by-step article on what needs > to be entered in the /etc/fstab to allow us to leave the drive connected > and facilitate auto mount/umount across system reboots; the results Google > are presenting isn__t sufficient. Perhaps it__s or search terms that aren__t > on point. > > Thanks. The following link provides a 'recipe' for using gpart to partition the disk. http://scratching.psybermonkey.net/2010/06/freebsd-how-to-format-partition.html If you use the '-L' flag to newfs after creating one or more partitions, e.g. newfs -L "image" daXp1 This will create a device node in /dev/ufs (/dev/ufs/image). You may then create fstab entries as usual, but using the label device, e.g. /dev/ufs/image /usr/image ufs rw 2 2 Unless you add "noauto" to the options (rw,noauto) the system will fsck and mount the partition on boot. You can, of course, create several partitions on the disk, using a separate label (-L) for each. Is this what you needed? ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
