[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/1381968
** Changed in: linux (Ubuntu)
Assignee: Andy Whitcroft (apw) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1381968
Title:
Fstrim destroys data on loopback device
To manage
JDownloader, could you please provide an offline apport-collect as
outlined in
https://help.ubuntu.com/community/ReportingBugs#Filing_bugs_when_offline_or_using_a_headless_setup
? This wouldn't require rebooting.
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You
** Tags removed: kernel-key
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1381968
Title:
Fstrim destroys data on loopback device
To manage notifications about this bug
@Andy: any news about this? can you reproduce? maybe any better place to
report this bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1381968
Title:
Fstrim destroys data on loopback device
To
Would be nice to know if anyone else can confirm this bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1381968
Title:
Fstrim destroys data on loopback device
To manage notifications about this
** Tags added: kernel-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1381968
Title:
Fstrim destroys data on loopback device
To manage notifications about this bug go to:
Do you need any more information? Could you reproduce the bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1381968
Title:
Fstrim destroys data on loopback device
To manage notifications about
** Changed in: linux (Ubuntu)
Importance: Undecided = Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1381968
Title:
Fstrim destroys data on loopback device
To manage notifications about
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Andy Whitcroft (apw)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1381968
Title:
Fstrim destroys data on loopback device
To manage
I have attempted to reproduce this on both Utopic and Trusty (14.04)
without success, below is a transcript of my attempt on Trusty. This is
with the latest Trusty main kernel. Perhaps you could confirm this
script correctly repeats your reproduce steps. If so then there must be
a system
Here is the actual script i am using to implement your reproduction
script in the description.
** Attachment added: repro
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1381968/+attachment/4238850/+files/repro
--
You received this bug notification because you are a member of Ubuntu
I will try your script and also provide output to show the dataloss on
my side
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1381968
Title:
Fstrim destroys data on loopback device
To manage
I could reproduce the issue by adding a single sync. It seems the
umount in original script flushes data to loopdevice. When the caches
are already flushed you will be able to reproduce the dataloss!
Btw..fsck seems unable to detect the broken filesystem!?
PS: I changed from mdadm to normal
*** before mount ...
17M -rw-r--r-- 1 root root 1001M Oct 17 13:32 /root/lp1381961/sparse-file
*** copy files ...
*** sync ...
*** du before trim...
16K /root/lp1381961/mnt/lost+found
342M/root/lp1381961/mnt/.jd_home
342M/root/lp1381961/mnt
*** before trim ...
364M -rw-r--r-- 1 root
sorry, somehow assigned to wrong package
** Package changed: openjdk-6 (Ubuntu) = linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1381968
Title:
Fstrim destroys data on loopback
Sorry , just noticed that I reported this bug in wrong project. Must be
assigned to kernel!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1381968
Title:
Fstrim destroys data on loopback device
To
I could not create missing logs because of:
It appears you are currently running a mainline kernel
I've upgraded to mainline kernel 3.17.1-031701-generic #201410150735, thought
it maybe contains a bugfix for this.
As the server runs in production-environment a restart is not that easy.
I've
18 matches
Mail list logo
