problems with nfs+TCP - Resource temporarily unavailable
Oliver Lehmann
lehmann at ans-netz.de
Thu May 26 02:34:33 PDT 2005
Oliver Lehmann wrote:
> Hi Mohan,
>
> Mohan Srinivasan wrote:
>
>
> > Is this consistently reproducible ?
>
> it is - everytime
I found out that I can reproducible make it work by writing on an other
harddisk.
file:/mnt/files 151368706 109165638 30093572 78% /mnt/files
file:/usr/ports 18162862 8410690 8299144 50% /usr/ports
file:/mnt/backups 19324310 17016301 762065 96% /mnt/tmp
writing to /mnt/files... we know what happend. But writing to /usr/ports
works w/o an error:
root at kartoffel olivleh1> umount /usr/ports/
root at kartoffel olivleh1> mount_nfs -T -3 -o soft,bg nudel:/usr/ports
/usr/ports
root at kartoffel olivleh1> dd if=/usr/tmp.data of=/usr/ports/tmp.data bs=32k
3200+0 records in
3200+0 records out
104857600 bytes transferred in 9.905884 secs (10585385 bytes/sec)
root at kartoffel olivleh1> dd if=/usr/tmp.data of=/usr/ports/tmp.data bs=32k
3200+0 records in
3200+0 records out
104857600 bytes transferred in 9.566243 secs (10961210 bytes/sec)
root at kartoffel olivleh1> umount /mnt/backups/
root at kartoffel olivleh1> mount_nfs -T -3 -o soft,bg file:/mnt/backups
/mnt/backups
root at kartoffel olivleh1> dd if=/usr/tmp.data of=/mnt/backups/tmp.data
bs=32k
dd: /mnt/backups/tmp.data: Resource temporarily unavailable
674+0 records in
673+0 records out
22052864 bytes transferred in 16.141799 secs (1366196 bytes/sec)
root at kartoffel olivleh1> dd if=/usr/tmp.data of=/mnt/backups/tmp.data
bs=32k
dd: /mnt/backups/tmp.data: Resource temporarily unavailable
242+0 records in
241+0 records out
7897088 bytes transferred in 7.301958 secs (1081503 bytes/sec)
on file (which is a nickname for nudel)
root at nudel olivleh1> df
Filesystem 1K-blocks Used Avail Capacity Mounted on
/dev/ad0s1a 257838 132236 104976 56% /
devfs 1 1 0 100% /dev
/dev/ad0s1d 257838 22888 214324 10% /tmp
/dev/ad0s1f 18162862 8410690 8299144 50% /usr
/dev/ad0s1e 257838 111122 126090 47% /var
/dev/ad5s1 151368706 109198438 30060772 78% /mnt/files
/dev/ad6s1 19324310 17023989 754377 96% /mnt/backups
/dev/da0s1e 4304663 2568753 1391537 65% /mnt/documents
ad0: 19092MB <ST320413A/3.39> [38792/16/63] at ata0-master UDMA33
ad5: 152627MB <SAMSUNG SP1604N/TM100-23> [310101/16/63] at ata2-slave
UDMA100
ad6: 19470MB <QUANTUM FIREBALLlct10 20/A03.0900> [39560/16/63] at
ata3-master UDMA66
atapci0: <Intel PIIX4 UDMA33 controller> port
0xf000-0xf00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0
ata0: channel #0 on atapci0
ata1: channel #1 on atapci0
atapci1: <SiI 0680 UDMA133 controller> port 0x8800-0x880f,0x8400-0x8403,
0x8000-0x8007,0x7c00-0x7c03,0x7800-0x7807 mem 0xe0405000-0xe04050ff irq
16 at device 13.0 on pci0
ata2: channel #0 on atapci1
ata3: channel #1 on atapci1
dmesg shows me no errors neither regarding ad5 nor ata2-master. smartctl
shows no recorded errors for ad5 for example. I'm wondering what is wrong
with atapci1
Any ideas whats going wrong?
--
Oliver Lehmann
http://www.pofo.de/
http://wishlist.ans-netz.de/
More information about the freebsd-current
mailing list