On 04/08/2017 01:16 PM, Hans van Kranenburg wrote: > On 04/07/2017 11:25 PM, Hans van Kranenburg wrote: >> Ok, I'm going to revive a year old mail thread here with interesting new >> info: >> >> [...] >> >> Now, another surprise: >> >> From the exact moment I did mount -o remount,nossd on this filesystem, >> the problem vanished. >> >> https://syrinx.knorrie.org/~knorrie/btrfs/keep/2017-04-07-ichiban-munin-nossd.png >> >> I don't have a new video yet, but I'll set up a cron tonight and post it >> later. >> >> I'm going to send another mail specifically about the nossd/ssd >> behaviour and other things I found out last week, but that'll probably >> be tomorrow. > > Well, there it is: > > https://syrinx.knorrie.org/~knorrie/btrfs/keep/2017-04-08-ichiban-walk-nossd.mp4 > > Amazing... :) I'll update the file later with extra frames.
Added all new pngs up until now to the video, same link to the mp4. Looks great! It just keeps reusing the same spots of space all the time. When looking at this, I can understand that this is an unwanted write pattern on a low-end ssd that was available for sale in 2008. But, how does this apply to an SSD you can buy in 2017? -- Hans van Kranenburg -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
