Date: Sat, 2 Apr 2005 11:18:35 GMT From: naxa lite adf <naxalite_adf@yahoo.com> To: freebsd-gnats-submit@FreeBSD.org Subject: misc/79441: problem writing on mounted msdos-fs at /mnt on HP Proliant DL380 Message-ID: <200504021118.j32BIZln015412@www.freebsd.org> Resent-Message-ID: <200504021120.j32BK6BM042140@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 79441 >Category: misc >Synopsis: problem writing on mounted msdos-fs at /mnt on HP Proliant DL380 >Confidential: no >Severity: non-critical >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Apr 02 11:20:05 GMT 2005 >Closed-Date: >Last-Modified: >Originator: naxa lite adf >Release: 5.3 Release and 5.4Beta1 >Organization: non-profit organization >Environment: Using FreeBSD 5.4 Beta1 and GENERIC kernel. >Description: floppy disks via "mount -t msdos /dev/fd0 /mnt" command, the floppy is mounted to /mnt successfully. However whenever i try to edit the a file on /mnt (floppy disk) the system spews out an error message: fsync: giving up on dirty: 0xc4d4de70: tag msdosfs, type VREG, usecount 1 flags (VV_OBJBUF), lock type msdosfs: EXCL (count 1) by thread 0xc47264b0 (pid) 471 I tried several "known good" and fresh 1.44 floppies and got the same error. whenever i try to force writing into it the system mysteriously reboots. A copy of my dmesg files is here: Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.4-BETA1 #0: Fri Mar 18 09:28:57 UTC 2005 root@harlow.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.06GHz (3056.51-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 Features=0xbfebfbff Hyperthreading: 2 logical CPUs real memory = 3221200896 (3071 MB) avail memory = 3150831616 (3004 MB) ACPI APIC Table: MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-15 on motherboard ioapic1 irqs 16-31 on motherboard ioapic2 irqs 32-47 on motherboard ioapic3 irqs 48-63 on motherboard npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x 920-0x923 on acpi0 cpu0: on acpi0 pcib0: on acpi0 pci0: on pcib0 pci0: at device 3.0 (no driver attached) pci0: at device 4.0 (no driver attached) pci0: at device 4.2 (no driver attached) isab0: at device 15.0 on pci0 isa0: on isab0 atapci0: port 0x2000-0x200f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 15.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 ohci0: mem 0xeeef0000-0xeeef0fff irq 7 at device 15.2 on pci0 usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered pcib1: on acpi0 pci1: on pcib1 ciss0: port 0x3000-0x30ff mem 0xf04f0000-0xf04f3fff,0xf05c0000-0xf05fffff irq 30 at device 3.0 on pci1 pcib2: on acpi0 pci2: on pcib2 bge0: mem 0xf06f0000-0xf06fffff irq 29 at device 1.0 on pci2 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000ba seTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:11:0a:! 9d:de:ef bge1: mem 0xf06e0000-0xf06effff irq 31 at device 2.0 on pci2 miibus1: on bge1 brgphy1: on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: Ethernet address: 00:11:0a:9d:de:ee pcib3: on acpi0 pci3: on pcib3 pcib4: on acpi0 pci6: on pcib4 pci6: at device 30.0 (no driver attached) acpi_tz0: on acpi0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 sio0: port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A fdc0: port 0x3f2-0x3f5 irq 6 drq 2 on acpi0 fd0: <1440-KB 3.5" drive> on fdc0 drive 0 orm0: at iomem 0xee000-0xeffff,0xc8000-0xcbfff,0xc0000-0xc7fff on isa0 pmtimer0 on isa0 ppc0: parallel port not found. sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounter "TSC" frequency 3056505180 Hz quality 800 Timecounters tick e very 10.000 msec acd0: CDROM at ata0-master PIO4 da0 at ciss0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-0 device da0: 135.168MB/s transfers da0: 347295MB (711261810 512 byte sectors: 255H 63S/T 44274C) Mounting root from ufs:/dev/da0s1a fsync: giving up on dirty: 0xc4d4de70: tag msdosfs, type VREG, usecount 1, writecount 1, refcount 1, flags (VV_OBJBUF), lock type msdosfs: EXCL (count 1) by thread 0xc47264b0 (pid 471) startcluster 388, dircluster 0, diroffset 672, on dev (4, 10) >How-To-Repeat: I have two identical machines, i installed 5.3 and 5.4beta1 on both and got the same error messages pertaining to fsync giving up on dirty.... im very sure that the floppies i inserted were all readble on OpenBSD and NetBSD, even on 4.x machines. Another odd thing is on all the saved vi sessions i attempted on both 5 versions, when i read those files on other machines, its all garbage like <F6><F6> on the entire page. I tried installing 4.11 on both machines and did not experience any problems regarding fsync when mounting the same floppies. Also i tried installing 5.3 on a different machine, on an intel dual xeon as well (asus barebone server) it didnt have any problems. Based on my tests, there seems to be a quirk on these machines. >Fix: ????? If there's any fix or suggestions thanks in advance as im at odds if im going to use 5.x series on a production environment. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200504021118.j32BIZln015412>