Opened 15 years ago

Closed 6 years ago

Last modified 5 years ago

#4547 closed bug (duplicate)

copy a new file on a NFS mount -> "PANIC"

Reported by: jedie Owned by: mmu_man
Priority: normal Milestone:
Component: File Systems/NFS Version: R1/alpha1
Keywords: Cc:
Blocked By: #5496 Blocking:
Platform: All

Description

I get a "PANIC" if i copy a new file on a NFS mount (Ubuntu Linux).

Here the last syslog lines:

KERN: nfs: mount(5, <NULL>, 00000000)
KERN: nfs: nfs_params: nfs:192.168.3.200:/home/jens/NFS,uid=0,gid=0,hostname=shredder
KERN: nfs:ip!
KERN: IP:192.168.3.200
KERN: nfs:hn!
KERN: nfs:uid!
KERN: nfs:gid!
KERN: nfs: ip:c0a80714 server:'192.168.3.200' export:'/home/jens/NFS' hostname:'shredder' uid=0 gid=0 
KERN: nfs: postoffice: can't find pending call to remove for xid 0
Last message repeated 1 time
KERN: nfs: mountd at 1407a8c0:52042
KERN: nfs: nfsd at 1407a8c0:2049
KERN: vnode 5:6695488 is not becoming unbusy!
KERN: vm_soft_fault: va 0x0 not covered by area in address space
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x10, ip 0x58fbc9, write 0, user 1, thread 0xba
KERN: vm_page_fault: thread "w>/boot/home/NFS" (186) in team "Tracker" (91) tried to read address 0x10, ip 0x58fbc9 ("libtracker.so_seg0ro" +0x114bc9)
KERN: bfs: bfs_create_index:2040: File or Directory already exists
Last message repeated 1 time

(Ticket moved from: ticket:3500#comment:3 )

Change History (2)

comment:1 by waddlesplash, 6 years ago

Blocked By: 5496 added
Resolution: duplicate
Status: newclosed

comment:2 by nielx, 5 years ago

Milestone: R1

Remove milestone for tickets with status = closed and resolution != fixed

Note: See TracTickets for help on using tickets.