* Daniel Kobras <kob...@debian.org> [201009, 00:42]: > Hi! > > We're not actually dirtying the blkdev, noflushd only opens it for writing > because that's what fsync() requires. The kernel cannot second guess what > dirty > tricks we're about to play and assumes we're about to change vital data. > >From a quick look at current kernel sources, it seems that the BLKFLSBUF > ioctl() nowadays provides us with all the functionality we need, but unlike > fsync() doesn't require a writable fd. If that doesn't work out, I'm inclined > to just end-of-life the daemon. I'm surprised it's of any use with modern > filesystems, anyway. > > Regards, > > Daniel. >
Hi Daniel and Marco! I'm afraid I don't understand well what is going on among udev, noflushd and kernel 2.6.30. Neither is it clear to me what you Daniel are suggesting with "...to just end-of.life the daemon": does that meab that I should stop noflushd? In this case, as I have already experienced, my idle disks would not stop spinning! Regards, Ennio -- [Perche' usare Win$ozz (dico io) se ..."anche uno sciocco sa farlo. \\?// Fa' qualche cosa di cui non sei capace!" (diceva Henry Miller) ] (°|°) Ricevo solo messaggi Content-Type: plain/text (no html o multipart). )=( !!! --> e-mail a mio nome via OE (M$) sono false e infette <-- !!! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
