Re: UFS Bug: FreeBSD 6.1/6.2/7.0: MOKB-08-11-2006, CVE-2006-5824, MOKB-03-11-2006, CVE-2006-5679
On Sat, Nov 25, 2006 at 01:20:33PM +0100, O. Hartmann wrote: Scott Long wrote: Kevin Oberman wrote: Date: Fri, 24 Nov 2006 15:58:39 -0700 From: Scott Long [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] David Malone wrote: These two bugs are shown for FreeBSD only and I guess, Solaris and other BSDs still use UFS. Are they more robust against this exploit or type of exploit? I don't know of a concerted effort by anyone to improve UFS in this way. I would guess that the odd bug would have been resolved, but no large scale work. David. Another thing to keep in mind is that filesystem mounting is only available to the super-user. If a feature came along such as automatically mounting USB drives, these bugs would indeed be critical. But for now, they are not. Not on the base system, but Gnome 2.16 with hald running will mount a removable device automatically. The standard configuration of Gnome runs hald. Allowing user mounts of removable media is even formalized by the addition of /media to hier(7). I'm not sure this should simply be treated as not being significant. Would it be possible to restrict Gnome to only auto-mounting msdos and cd9660 filesystems? Scott ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] Sorry, if my question may sound heretic, but wouldn't it be more sophisticated solving the problem instead of disabling everything what could trigger the bug? It's been explained to you why solving the problem (i.e. adapting UFS so that no combination of corrupted filesystem data can cause a panic) is, in all practical senses, probably impossible. To recap, it would require fundamentally redesigning the UFS code to perform input validation before using any on-disk data, and adding some kind of backout and recovery strategies for when bad data is detected. Apart from the significant additional complexity, this may have an unacceptable runtime performance penalty. I hope the status of this issue is clear now. Kris pgpfp4eLln0db.pgp Description: PGP signature
Re: Problems unmounting/fssyncking extern UFS filesystem
On Sat, Nov 25, 2006 at 05:08:03PM +0100, O. Hartmann wrote: A while ago since now I receive kernel messages like this in FreeBSD 6.2-PRE/AMD64: fsync: giving up on dirty 0xff000362c7c0: tag devfs, type VCHR usecount 1, writecount 0, refcount 325 mountedhere 0xff00504d8400 flags () v_object 0xff00013c80e0 ref 0 pages 1286 lock type devfs: EXCL (count 1) by thread 0xff0050287260 (pid 14109) dev ufs/BACKUP Filesystem is an external USB attached SATA HD, ohci() driven (due to ehci() is not working stable and properly on FreeBSD 6.2). Filesystem is mounted via amd() and there via the'script' option in amd() due to problems of the amd() mounting process recognizing UFS filesystems. After 30 seconds of inactivity the filesystems gets dismounted. This worked quite well in the past, but now I see this kernel error messages. Before doing a PR, I would like to serious ask whether this is an issue or not. It's not a serious issue, AFAIK. Kris pgpUE3sLPh2y8.pgp Description: PGP signature
kqueue LOR
Hi, the attached lor.txt contains LOR I got this yesterday. It is FreeBSD 6.1 with relatively recent kernel, from last week or so. -- VH +lock order reversal: + 1st 0xc537f300 kqueue (kqueue) @ /usr/src/sys/kern/kern_event.c:1547 + 2nd 0xc45c22dc struct mount mtx (struct mount mtx) @ /usr/src/sys/ufs/ufs/ufs_vnops.c:138 +KDB: stack backtrace: +kdb_backtrace(c07f9879,c45c22dc,c07fd31c,c07fd31c,c080c7b2,...) at kdb_backtrace+0x2f +witness_checkorder(c45c22dc,9,c080c7b2,8a,c07fc6bd,...) at witness_checkorder+0x5fe +_mtx_lock_flags(c45c22dc,0,c080c7b2,8a,e790ba20,...) at _mtx_lock_flags+0x32 +ufs_itimes(c47a0dd0,c47a0e90,e790ba78,c060e1cc,c47a0dd0,...) at ufs_itimes+0x6c +ufs_getattr(e790ba54,e790baec,c0622af6,c0896f40,e790ba54,...) at ufs_getattr+0x20 +VOP_GETATTR_APV(c0896f40,e790ba54,c08a5760,c47a0dd0,e790ba74,...) at VOP_GETATTR_APV+0x3a +filt_vfsread(c4cf261c,6,c07f445e,60b,0,...) at filt_vfsread+0x75 +knote(c4f57114,6,1,1f30c2af,1f30c2af,...) at knote+0x75 +VOP_WRITE_APV(c0896f40,e790bbec,c47a0dd0,227,e790bcb4,...) at VOP_WRITE_APV+0x148 +vn_write(c45d5120,e790bcb4,c5802a00,0,c4b73a80,...) at vn_write+0x201 +dofilewrite(c4b73a80,1b,c45d5120,e790bcb4,,...) at dofilewrite+0x84 +kern_writev(c4b73a80,1b,e790bcb4,8220c71,0,...) at kern_writev+0x65 +write(c4b73a80,e790bd04,c,c07d899c,3,...) at write+0x4f +syscall(3b,3b,bfbf003b,0,bfbfeae4,...) at syscall+0x295 +Xint0x80_syscall() at Xint0x80_syscall+0x1f +--- syscall (4, FreeBSD ELF32, write), eip = 0x2831d727, esp = 0xbfbfea1c, ebp = 0xbfbfea48 --- signature.asc Description: OpenPGP digital signature
Re: FreeBSD 6.2-PRE panic
On Sat, Nov 25, 2006 at 05:26:38PM +, Robert Watson wrote: Has GNATS been fixed? I mean its search (by ID or single line fields). Apparently the mirror of the GNATS database on the web server had become corrupted; Ken Smith has apparently fixed this, and it looks like the database is now up-to-date again. Give it a try? It works now. Thanks! Eugene ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sshfs/nfs cause server lockup
On 23/11/06, Kris Kennaway [EMAIL PROTECTED] wrote: On Thu, Nov 23, 2006 at 04:38:48PM +0100, [EMAIL PROTECTED] wrote: Chris [EMAIL PROTECTED] wrote: kris a development on this, someone else posted about a nfs problem and reading his post some starkling point he made about network cards, he stated he only gets the bug on sis rl and fxp. Sorry for the misunderstanding, but I think that the 'NFS via TCP' thread covers other bugs, ie the inability to mount NFS v3 over TCP. I've tested the cards above, and the person I replied to encountered the same bug with a bge card. My solution was to remove custom nfs settings in sysctl.conf. I don't know which one was the culprit because I don't have the time to look into it further. My poking uncovered a set of crashing bugs and potentially a livelock. I would agree that NFS is very fragile in RELENG_6. So far fingers crossed I've not run into an NFS server deadlock you described. Are you sure these are NFS problems and not ethernet driver problems? Kris The consistency is the servers that lock up are fine when not using any nfs or sshfs mounts. But the 2 servers that are fine use dc and re network adaptors. I am not able to setup my local bsd box until a new hd arrives next monday and will be a day or so before I get it setup to mirror the production conditions of the servers and I will then mount some nfs on it to repeat the problem. Chris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsd-update to track release engineering
Colin Percival wrote: Petr Holub wrote: I'm working on it. If I install RC1 now, would it be possible to upgrade to RC2 and RELEASE, or is it not ready yet? My intention is that anyone running 6.1-RELEASE, 6.2-BETA*, or 6.2-RC* will be able to upgrade to the latest release candidate or release. To avoid repeating myself too many times, I'm just going to point to my latest blog entry: http://www.daemonology.net/blog/2006-11-26-freebsd-6.1-to-6.2-binary-upgrade.html Colin Percival ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: UFS Bug: FreeBSD 6.1/6.2/7.0: MOKB-08-11-2006, CVE-2006-5824, MOKB-03-11-2006, CVE-2006-5679
On Fri, 24 Nov 2006, Kevin Oberman wrote: I don't know of a concerted effort by anyone to improve UFS in this way. I would guess that the odd bug would have been resolved, but no large scale work. Another thing to keep in mind is that filesystem mounting is only available to the super-user. If a feature came along such as automatically mounting USB drives, these bugs would indeed be critical. But for now, they are not. Not on the base system, but Gnome 2.16 with hald running will mount a removable device automatically. The standard configuration of Gnome runs hald. Allowing user mounts of removable media is even formalized by the addition of /media to hier(7). I'm not sure this should simply be treated as not being significant. At least for now, untrusted UFS file systems should not be mounted without first performing a file system check on them. I'd like to see resilience improved so that we're not dealing with panic scenarios on a heavily corrupted UFS, but it's fairly well documented that we consider file systems to be in one of three states: clean, in which case they are by definition not corrupt, requiring a bgfsck (i.e., garbage collection following a fail stop with soft updates enabled), or dirty (requiring a full fsck before mount). I think a better target for resilience improvements is actually msdosfs, since users are far more likely to want to deal with potentially currupted FAT file systems from USB devices than UFS file systems from arbitrary sources. And, unlike UFS, it's fairly likely someone with only moderate VFS/VM background could do the basics of this work, with an immediate practical benefit. Robert N M Watson Computer Laboratory University of Cambridge ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[msdosfs] [patch] msdosfs incorrectly handles NT 8.3 capitalization
Hello, More than a year ago I discovered a bug in msdosfs incorrectly handling NT 8.3 capitalization. It was discussed on the lists and Micah prepared a patch and filed this PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=86655 Unfortunately, it seems to have been forgotten. Can some of the committers have a look at it please ?? Many thanks, Martin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [msdosfs] [patch] msdosfs incorrectly handles NT 8.3 capitalization
On Sun, 26 Nov 2006, 16:37+0100, martinko wrote: Hello, More than a year ago I discovered a bug in msdosfs incorrectly handling NT 8.3 capitalization. It was discussed on the lists and Micah prepared a patch and filed this PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=86655 Unfortunately, it seems to have been forgotten. Can some of the committers have a look at it please ?? Fixed in HEAD. Will MFC the code to RELENG_6 in three weeks. -- Maxim Konovalov ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kqueue LOR
On Sun, 26 Nov 2006, Václav Haisman wrote: Hi, the attached lor.txt contains LOR I got this yesterday. It is FreeBSD 6.1 with relatively recent kernel, from last week or so. lock order reversal: 1st 0xc537f300 kqueue (kqueue) @ sys/kern/kern_event.c:1547 2nd 0xc45c22dc struct mount mtx (struct mount mtx) @ sys/ufs/ufs/ufs_vnops.c:138 Added to The LOR page with LOR ID # 193: http://sources.zabbadoz.net/freebsd/lor.html#193 -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_6_2 tinderbox] failure on amd64/amd64
TB --- 2006-11-26 20:50:43 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2006-11-26 20:50:43 - starting RELENG_6_2 tinderbox run for amd64/amd64 TB --- 2006-11-26 20:50:43 - cleaning the object tree TB --- 2006-11-26 20:50:43 - checking out the source tree TB --- 2006-11-26 20:50:43 - cd /tinderbox/RELENG_6_2/amd64/amd64 TB --- 2006-11-26 20:50:43 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_6_2 src TB --- 2006-11-26 21:00:54 - WARNING: /usr/bin/cvs returned exit code 1 TB --- 2006-11-26 21:00:54 - ERROR: unable to check out the source tree TB --- 2006-11-26 21:00:54 - tinderbox aborted TB --- 0.05 user 0.00 system 610.68 real http://tinderbox.des.no/tinderbox-releng_6-RELENG_6_2-amd64-amd64.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Large msdosfs disk will not mount on RELENG_6
I just bought a large external hard drive for home backups (500g Western Digital My Book). When I plug it in to my machine (RELENG_6 from about a week ago), the system sees the device just fine: Nov 26 22:03:21 neptune kernel: umass0: Western Digital External HDD, rev 2.00/1.06, addr 2 Nov 26 22:03:21 neptune kernel: uhid1: Western Digital External HDD, rev 2.00/1.06, addr 2, iclass 8/6 Nov 26 22:03:21 neptune kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Nov 26 22:03:21 neptune kernel: da0: WD 5000YS External 106a Fixed Direct Access SCSI-4 device Nov 26 22:03:21 neptune kernel: da0: 40.000MB/s transfers Nov 26 22:03:21 neptune kernel: da0: 476940MB (976773168 512 byte sectors: 255H 63S/T 60801C) But when I try to mount the drive (mount -t msdos /dev/da0 /mnt), the system gives the following error: Nov 26 22:06:41 neptune kernel: mountmsdosfs(): disk too big, sorry I was surprised to see a file system limitation on FreeBSD that Windows does not have. I will probably reformat the system to ufs2, but thought I would mention this error message. I'm sure these drives will become increasingly common. Richard Coleman [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Large msdosfs disk will not mount on RELENG_6
- Original Message - From: Richard Coleman [EMAIL PROTECTED] To: freebsd-stable@freebsd.org Sent: Monday, November 27, 2006 5:23 AM Subject: Large msdosfs disk will not mount on RELENG_6 I just bought a large external hard drive for home backups (500g Western Digital My Book). When I plug it in to my machine (RELENG_6 from about a week ago), the system sees the device just fine: Nov 26 22:03:21 neptune kernel: umass0: Western Digital External HDD, rev 2.00/1.06, addr 2 Nov 26 22:03:21 neptune kernel: uhid1: Western Digital External HDD, rev 2.00/1.06, addr 2, iclass 8/6 Nov 26 22:03:21 neptune kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Nov 26 22:03:21 neptune kernel: da0: WD 5000YS External 106a Fixed Direct Access SCSI-4 device Nov 26 22:03:21 neptune kernel: da0: 40.000MB/s transfers Nov 26 22:03:21 neptune kernel: da0: 476940MB (976773168 512 byte sectors: 255H 63S/T 60801C) But when I try to mount the drive (mount -t msdos /dev/da0 /mnt), the system gives the following error: Nov 26 22:06:41 neptune kernel: mountmsdosfs(): disk too big, sorry I was surprised to see a file system limitation on FreeBSD that Windows does not have. I will probably reformat the system to ufs2, but thought I would mention this error message. I'm sure these drives will become increasingly common. Richard Coleman [EMAIL PROTECTED] I am very suprised at all that windows would allow you to format a 500G drive into a single 500G FAT32 partition. As far as I am aware windows 2000 and xp will only allow you to format up to a 32G dive with FAT32. Any bigger and it will force you to use NTFS. The other strange thing is tht you are trying to mount /dev/da0 and not /dev/de0s1. How did you format this drive ? -Clay ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Large msdosfs disk will not mount on RELENG_6
On Sun, 2006-11-26 at 19:23, Richard Coleman wrote: I just bought a large external hard drive for home backups (500g Western Digital My Book). When I plug it in to my machine (RELENG_6 from about a week ago), the system sees the device just fine: Nov 26 22:03:21 neptune kernel: umass0: Western Digital External HDD, rev 2.00/1.06, addr 2 Nov 26 22:03:21 neptune kernel: uhid1: Western Digital External HDD, rev 2.00/1.06, addr 2, iclass 8/6 Nov 26 22:03:21 neptune kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Nov 26 22:03:21 neptune kernel: da0: WD 5000YS External 106a Fixed Direct Access SCSI-4 device Nov 26 22:03:21 neptune kernel: da0: 40.000MB/s transfers Nov 26 22:03:21 neptune kernel: da0: 476940MB (976773168 512 byte sectors: 255H 63S/T 60801C) But when I try to mount the drive (mount -t msdos /dev/da0 /mnt), the system gives the following error: Nov 26 22:06:41 neptune kernel: mountmsdosfs(): disk too big, sorry I was surprised to see a file system limitation on FreeBSD that Windows does not have. I will probably reformat the system to ufs2, but thought I would mention this error message. I'm sure these drives will become increasingly common. Would you share how you initialized this drive, and what parameters you used? FAT32 has a 2 TB limit for the filesystem and 2 GB for a file. The error you saw is thrown when the # of sectors exceeds an unsigned 32 bit integer. BTW, the limit is based on the DOS spec, not FreeBSD. jim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Large msdosfs disk will not mount on RELENG_6
On Nov 27, 2006, at 1:09 , Clayton Milos wrote: I just bought a large external hard drive for home backups (500g Western Digital My Book). When I plug it in to my machine (RELENG_6 from about a week ago), the system sees the device just fine: I am very suprised at all that windows would allow you to format a 500G drive into a single 500G FAT32 partition. As far as I am aware windows 2000 and xp will only allow you to format up to a 32G dive with FAT32. Any bigger and it will force you to use NTFS. The other strange thing is tht you are trying to mount /dev/da0 and not /dev/de0s1. How did you format this drive ? It comes formatted FAT32. I bought one last week as well, and tried to mount it to extract the included software before repartitioning. I finally mounted it on an OSX box to copy the software to CDR. -- brandon s. allbery[linux,solaris,freebsd,perl] [EMAIL PROTECTED] system administrator [openafs,heimdal,too many hats] [EMAIL PROTECTED] electrical and computer engineering, carnegie mellon universityKF8NH ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Large msdosfs disk will not mount on RELENG_6
Clayton Milos wrote: - Original Message - From: Richard Coleman [EMAIL PROTECTED] To: freebsd-stable@freebsd.org Sent: Monday, November 27, 2006 5:23 AM Subject: Large msdosfs disk will not mount on RELENG_6 I just bought a large external hard drive for home backups (500g Western Digital My Book). When I plug it in to my machine (RELENG_6 from about a week ago), the system sees the device just fine: Nov 26 22:03:21 neptune kernel: umass0: Western Digital External HDD, rev 2.00/1.06, addr 2 Nov 26 22:03:21 neptune kernel: uhid1: Western Digital External HDD, rev 2.00/1.06, addr 2, iclass 8/6 Nov 26 22:03:21 neptune kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Nov 26 22:03:21 neptune kernel: da0: WD 5000YS External 106a Fixed Direct Access SCSI-4 device Nov 26 22:03:21 neptune kernel: da0: 40.000MB/s transfers Nov 26 22:03:21 neptune kernel: da0: 476940MB (976773168 512 byte sectors: 255H 63S/T 60801C) But when I try to mount the drive (mount -t msdos /dev/da0 /mnt), the system gives the following error: Nov 26 22:06:41 neptune kernel: mountmsdosfs(): disk too big, sorry I was surprised to see a file system limitation on FreeBSD that Windows does not have. I will probably reformat the system to ufs2, but thought I would mention this error message. I'm sure these drives will become increasingly common. Richard Coleman [EMAIL PROTECTED] I am very suprised at all that windows would allow you to format a 500G drive into a single 500G FAT32 partition. As far as I am aware windows 2000 and xp will only allow you to format up to a 32G dive with FAT32. Any bigger and it will force you to use NTFS. The other strange thing is tht you are trying to mount /dev/da0 and not /dev/de0s1. How did you format this drive ? -Clay I didn't format it. This was out of the box. To be honest, I forgot to look to see how much of the disk that Windows XP could see. And I needed to use the drive, so unfortunately I've already nuked the msdosfs stuff and reformatted it with ufs2. Looking at the (meager) documentation that came with the drive, it just says that it was preformatted as a single FAT32 partition for compatibility. As to using da0 rather than da0s1, that's how I've always seen to mount a msdosfs partition (and it works for my 256M usb key drive). Richard Coleman [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Large msdosfs disk will not mount on RELENG_6
Hi Richard, On Sun, Nov 26, 2006 at 10:23:14PM -0500, Richard Coleman wrote: I just bought a large external hard drive for home backups (500g Western Digital My Book). When I plug it in to my machine (RELENG_6 from about a week ago), the system sees the device just fine: Nov 26 22:03:21 neptune kernel: umass0: Western Digital External HDD, rev 2.00/1.06, addr 2 Nov 26 22:03:21 neptune kernel: uhid1: Western Digital External HDD, rev 2.00/1.06, addr 2, iclass 8/6 Nov 26 22:03:21 neptune kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Nov 26 22:03:21 neptune kernel: da0: WD 5000YS External 106a Fixed Direct Access SCSI-4 device Nov 26 22:03:21 neptune kernel: da0: 40.000MB/s transfers Nov 26 22:03:21 neptune kernel: da0: 476940MB (976773168 512 byte sectors: 255H 63S/T 60801C) But when I try to mount the drive (mount -t msdos /dev/da0 /mnt), the system gives the following error: Nov 26 22:06:41 neptune kernel: mountmsdosfs(): disk too big, sorry I was surprised to see a file system limitation on FreeBSD that Windows does not have. I will probably reformat the system to ufs2, but thought I would mention this error message. I'm sure these drives will become increasingly common. Looking at /sys/fs/msdosfs/msdosfs_vfsops.c seems to hint the existance of options MSDOSFS_LARGE; this avoids the error message and will let you mount the disk. Perhaps it's time for an update of msdosfs(5) ? (I've CC-ed Tom Rhodes for this). Regards, -- Rink P.W. Springer- http://rink.nu It's you isn't it? THE BASTARD OPERATOR FROM HELL! In the flesh, on the phone and in your account... - BOFH #3 smime.p7s Description: S/MIME cryptographic signature
Re: Large msdosfs disk will not mount on RELENG_6
On Nov 27, 2006, at 1:26 , Richard Coleman wrote: As to using da0 rather than da0s1, that's how I've always seen to mount a msdosfs partition (and it works for my 256M usb key drive). Flash drives usually don't have partition tables. The WD drive does; I checked it with fdisk before trying to mount, because some vendors like to use s4 instead of s1 (hello Iomega : ) -- brandon s. allbery[linux,solaris,freebsd,perl] [EMAIL PROTECTED] system administrator [openafs,heimdal,too many hats] [EMAIL PROTECTED] electrical and computer engineering, carnegie mellon universityKF8NH ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Large msdosfs disk will not mount on RELENG_6
On Mon, Nov 27, 2006 at 07:34:09AM +0100, Rink Springer wrote: Looking at /sys/fs/msdosfs/msdosfs_vfsops.c seems to hint the existance of options MSDOSFS_LARGE; this avoids the error message and will let you mount the disk. Oh, and before I forget: this option is defined in /sys/conf/NOTES as well (a pure #ifdef in source code is not enough, of course :-) --- # Experimental support for large MS-DOS filesystems. # # WARNING: This uses at least 32 bytes of kernel memory (which is not # reclaimed until the FS is unmounted) for each file on disk to map # between the 32-bit inode numbers used by VFS and the 64-bit # pseudo-inode # numbers used internally by msdosfs. This is only safe to use in # certain # controlled situations (e.g. read-only FS with less than 1 million # files). # Since the mappings do not persist across unmounts (or reboots), these # filesystems are not suitable for exporting through NFS, or any other # application that requires fixed inode numbers. options MSDOSFS_LARGE --- Regards, -- Rink P.W. Springer- http://rink.nu It's you isn't it? THE BASTARD OPERATOR FROM HELL! In the flesh, on the phone and in your account... - BOFH #3 smime.p7s Description: S/MIME cryptographic signature
Re: Large msdosfs disk will not mount on RELENG_6
Christian Brueffer wrote: On Sun, Nov 26, 2006 at 10:23:14PM -0500, Richard Coleman wrote: I just bought a large external hard drive for home backups (500g Western Digital My Book). When I plug it in to my machine (RELENG_6 from about a week ago), the system sees the device just fine: Nov 26 22:03:21 neptune kernel: umass0: Western Digital External HDD, rev 2.00/1.06, addr 2 Nov 26 22:03:21 neptune kernel: uhid1: Western Digital External HDD, rev 2.00/1.06, addr 2, iclass 8/6 Nov 26 22:03:21 neptune kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Nov 26 22:03:21 neptune kernel: da0: WD 5000YS External 106a Fixed Direct Access SCSI-4 device Nov 26 22:03:21 neptune kernel: da0: 40.000MB/s transfers Nov 26 22:03:21 neptune kernel: da0: 476940MB (976773168 512 byte sectors: 255H 63S/T 60801C) But when I try to mount the drive (mount -t msdos /dev/da0 /mnt), the system gives the following error: Nov 26 22:06:41 neptune kernel: mountmsdosfs(): disk too big, sorry I was surprised to see a file system limitation on FreeBSD that Windows does not have. I will probably reformat the system to ufs2, but thought I would mention this error message. I'm sure these drives will become increasingly common. Please rebuild your kernel with options MSDOSFS_LARGE and try again. - Christian Ahh, good to know. I hadn't seen that one before. Thanks. Richard Coleman [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Large msdosfs disk will not mount on RELENG_6
On Sun, 2006-11-26 at 22:09, Clayton Milos wrote: As far as I am aware windows 2000 and xp will only allow you to format up to a 32G dive with FAT32. Any bigger and it will force you to use NTFS. The other strange thing is tht you are trying to mount /dev/da0 and not /dev/de0s1. The 32 gb restriction was artificial. You can look it up in the M$ knowledge base. Watch out for the hand waving. FreeBSD and Linux (and probably other cluefull OS's)can handle a 500gb FAT32 drive (assuming intelligent format values) w/o problem. The real issue with large FAT32 volumes is wasted space. You have to crank up the cluster size so small files eat way more on disk space than they should. Large directories don't perform all that well either. My problem with using them for container type backups is that my user partition is way bigger than 2gb, so a level 0 dump wouldn't fit. jim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Large msdosfs disk will not mount on RELENG_6
Rink Springer wrote: On Mon, Nov 27, 2006 at 07:34:09AM +0100, Rink Springer wrote: Looking at /sys/fs/msdosfs/msdosfs_vfsops.c seems to hint the existance of options MSDOSFS_LARGE; this avoids the error message and will let you mount the disk. Oh, and before I forget: this option is defined in /sys/conf/NOTES as well (a pure #ifdef in source code is not enough, of course :-) --- # Experimental support for large MS-DOS filesystems. # # WARNING: This uses at least 32 bytes of kernel memory (which is not # reclaimed until the FS is unmounted) for each file on disk to map # between the 32-bit inode numbers used by VFS and the 64-bit # pseudo-inode # numbers used internally by msdosfs. This is only safe to use in # certain # controlled situations (e.g. read-only FS with less than 1 million # files). # Since the mappings do not persist across unmounts (or reboots), these # filesystems are not suitable for exporting through NFS, or any other # application that requires fixed inode numbers. options MSDOSFS_LARGE --- Regards, It didn't occur to me to check NOTES, since this is on a very GENERIC box. I did check the man pages for both msdosfs and mount_msdosfs, as well as the storage chapter in the handbook. I didn't see this error message or that kernel option mentioned there. Richard Coleman [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
