[Expired for linux (Ubuntu Precise) because there has been no activity
for 60 days.]
** Changed in: linux (Ubuntu Precise)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1126367
T
[Expired for linux (Ubuntu Quantal) because there has been no activity
for 60 days.]
** Changed in: linux (Ubuntu Quantal)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
** Changed in: linux (Ubuntu Precise)
Status: Triaged => Incomplete
** Changed in: linux (Ubuntu Quantal)
Status: Triaged => Incomplete
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bug
This made it into mainline as of v3.8-rc7, so it should be fixed in
Raring.
However, I don't see that commit 5d1f402 was sent to upstream stable.
Can you confirm this bug still exists in the Precise and Quantal with
the latest updates? If it does still exist, I can send a request to
have this com
I've tested a variant of this patch built from the ubuntu mainline git
tree (3.7.0-7-generic), my variant was from the dev and had a printk
that was triggered when the bug would have happened without the fix. I
would have lost data 68 times over 16 days. The original discovery of
the bug is docum
Linus picked it up somewhere between 3.8rc6 and 3.8rc7, the gitweb entry
is here
https://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit;h=5d1f40202bad12d4c70a2d40a420b30d23a72b1a
This is new territory for me but I thought it was important enough to
try. I've been losing data for ov
Also, it's always best to get these fixes in upstream stable first. Do
you happen to know if that commit will be requested for inclusion in
upstream stable?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
I can build a test kernel with that commit cherry-picked in to Precise
and Quantal. Do you have a test system you could use to test this test
kernel?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/112
This appears to be upstream commit:
5d1f40202bad12d4c70a2d40a420b30d23a72b1a
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1126367
Title:
sparse files are sometimes truncated in btrfs
To manage not
** Also affects: linux (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Quantal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Precise)
Status: New => Triaged
** Changed in: linux (Ubuntu Quantal)
Status: New =>
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1126367
Title:
sparse files are sometimes truncated in btrfs
To manage notifications a
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1126367
Title:
sparse files are sometimes truncated in btrfs
To manage notificatio
13 matches
Mail list logo
