@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
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
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
Public bug reported:
I've upgraded Ubuntu Server 12.04 LTS to 14.04 LTS.
The setup contains a loopback device (/dev/loop3) mounted into a
software raid 1 (/dev/md2).
After the weekly cronjob (/etc/cron.weekly/fstrim) ran, I've discovered
that it wiped all data on the loopback device from the
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
no more java crashes.
greetings
jiaz (JD-Manager)
--
JDownloader crash on linux ubuntu 10.04
https://bugs.launchpad.net/bugs/644094
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
11 matches
Mail list logo
