** Changed in: linux (Ubuntu Oneiric)
Status: Triaged => Invalid
** Changed in: linux (Ubuntu Lucid)
Status: Confirmed => Invalid
** Changed in: bzr (Ubuntu Lucid)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.7 kernel[0] (Not a kernel in the daily directory) and install both
the linux-image and linux-image-extra .deb packages.
If this bug is fixed in the ma
This bug was filed against a series that is no longer supported and so
is being marked as Won't Fix. If this issue still exists in a supported
series, please file a new bug.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
This remains a serious bug in the NFS implementation in Linux, that has
persisted into the current releases. Reopening.
** Changed in: linux (Ubuntu)
Status: Won't Fix => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was filed against a series that is no longer supported and so
is being marked as Won't Fix. If this issue still exists in a supported
series, please file a new bug.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
I'm not an NFS/Bazaar developer so I'm not familiar with the details but
this bug is pretty serious in every day use when using NFS shares.
User "gpk" above mentioned this has something to do with sent
write/locking requests. Could it be possible to have an easy workaround
to this bug like modifyi
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Lucid)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/480444
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bzr (Ubuntu Lucid)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/480444
Title:
p
** Tags added: rls-mgr-o-tracking
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/480444
Title:
packet storm with linux NFSv4 client when calling ftruncate()
To manage notifications about this bug go
** Also affects: bzr (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: bzr (Ubuntu Oneiric)
Importance: Undecided
Status: Invalid
** Also affects: linux (Ubuntu Oneiric)
Impor
Ignore my last comment, sigh.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/480444
Title:
packet storm with linux NFSv4 client when calling ftruncate()
To manage notifications about this bug go to:
There was a bug in the bot that marked the bug watch task "Won't Fix".
That has been addressed. I apologize for any inconvenience.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/480444
Title:
packet
Reopening per slangaseks comment.
** Changed in: linux (Ubuntu)
Status: Won't Fix => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/480444
Title:
packet storm with linux NFSv4 client
This bug was filed against a series that is no longer supported and so
is being marked as Won't Fix. If this issue still exists in a supported
series, please file a new bug.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
This bug is still present in every release since karmic, up to and
including oneiric's 3.0 kernel.
** Tags removed: karmic
** Changed in: linux (Ubuntu)
Status: Won't Fix => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
This bug was filed against a series that is no longer supported and so
is being marked as Won't Fix. If this issue still exists in a supported
series, please file a new bug.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
it's still reproducible for me with a 2.6.38 client and the current
version of nfs-common in natty, which is 1.2.2. I am not at liberty to
upgrade the server (and this is a bug with a misbehaving client, in any
case).
--
You received this bug notification because you are a member of Ubuntu
Bugs,
After updating some packages, i can not reproduce:
- server & client: nfs-common 1.2.3-1, linux-image-2.6.38-1
- server: nfs-kernel-server 1.2.3, libgssglue 0.1-4
- client: libgssglue 0.2-2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Using bzr + nfsv4 i reproduce systematically ("bzr status" command
non-interruptible even with kill -9. Using "umount -f " once or twice
terminates bzr command).
I add log statements (logs added with 'mutter' are stored in ~/.bzr.log) in
"show_tree_status" from status.py. It appears that thi
The only way I can think of would be by taking some kind of memory image
via the kernel.
Unless you know a way, I think you'd best be happy with the strace output.
On 15/03/11 01:13, Robert Collins wrote:
> can you get a core perhaps?
>
--
You received this bug notification because you are a me
can you get a core perhaps?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/480444
Title:
packet storm with linux NFSv4 client when calling ftruncate()
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.
Can't do that. It's non-interruptible even with kill -9.
There is output from strace at https://bugs.launchpad.net/bugs/665082
On 14/03/11 21:42, Martin Pool wrote:
> To help us work out whether a workaround in bzr is possible, can someone
> please interrupt bzr at the point where this is happ
On Mon, Mar 14, 2011 at 09:42:02PM -, Martin Pool wrote:
> To help us work out whether a workaround in bzr is possible, can someone
> please interrupt bzr at the point where this is happening, and post the
> Python traceback that should be written into ~/.bzr.log.
No, the process is uninterrup
To help us work out whether a workaround in bzr is possible, can someone
please interrupt bzr at the point where this is happening, and post the
Python traceback that should be written into ~/.bzr.log.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
I think we may have experienced the same bug as noted here because
syslog shows sys_ftruncate().
I already posted a bug report here so this is a crosspost but I think this
could more proper bug report for our issue:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/578866/comments/4
I try to
On 24/10/10 00:32, Steve Langasek wrote:
> On Sat, Oct 23, 2010 at 09:42:27PM -, gpk wrote:
>> I looked at the packet storm (captured above), and it seems to be a rapid
>> repetition of a single
>> command and a single response.
>> The command is a COMPOUND of PUTFH, WRITE, GETATTR,
>> and th
On Sat, Oct 23, 2010 at 09:42:27PM -, gpk wrote:
> I looked at the packet storm (captured above), and it seems to be a rapid
> repetition of a single
> command and a single response.
> The command is a COMPOUND of PUTFH, WRITE, GETATTR,
> and the server responds with NFS4ERR_OPENMODE which is
I looked at the packet storm (captured above), and it seems to be a rapid
repetition of a single
command and a single response.
The command is a COMPOUND of PUTFH, WRITE, GETATTR,
and the server responds with NFS4ERR_OPENMODE which is
in response to a failure of the WRITE.
Now, it is odd that the
28 matches
Mail list logo
