@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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1381968
Title:
Fstrim destroys data on loopback d
Would be nice to know if anyone else can confirm this bug?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1381968
Title:
Fstrim destroys data on loopback device
Status in “linux” packag
Do you need any more information? Could you reproduce the bug?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1381968
Title:
Fstrim destroys data on loopback device
Status in “linux” pa
*** 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 ro
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 mou
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1381968
Title:
Fstrim destroys data on loopback device
St
sorry, somehow assigned to wrong package
** Package changed: openjdk-6 (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1381968
Title:
Fstrim destroys data on l
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 dete
8 matches
Mail list logo
