From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?iso-8859-2?B?o3VrYXN6IE1pZXJ6d2E=?= Subject: Re: reiser4 resize Date: Thu, 21 Sep 2006 09:49:08 +0200 Message-ID: References: <200609191723.01936.vs@namesys.com> <45102ED6.6080209@slaphack.com> <45123F81.4040909@slaphack.com> Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Return-path: list-help: list-unsubscribe: list-post: Errors-To: flx@namesys.com In-Reply-To: <45123F81.4040909@slaphack.com> List-Id: Content-Type: text/plain; format="flowed"; delsp="yes"; charset="iso-8859-1" To: David Masover , "reiserfs-list@namesys.com" Dnia Thu, 21 Sep 2006 09:30:09 +0200, David Masover =20 napisa=B3: > --- linux/fs/buffer.c 2006-08-15 20:40:36.504608696 -0500 > +++ linux/fs/buffer.c.new 2006-08-15 20:42:35.877461264 -0500 > @@ -366,12 +366,12 @@ > > asmlinkage long sys_fsync(unsigned int fd) > { > - return __do_fsync(fd, 0); > + return 0; > } > > asmlinkage long sys_fdatasync(unsigned int fd) > { > - return __do_fsync(fd, 1); > + return 0; > } > > /* I remember that I played a little with disabling sync in reiser4 sources, = it helped only for amarok (it's uses sqlite for storing statistic data and = =20 it writes to it on song change, sqlite calls sync and it ends up with =20 writeing to disk instead of playing a song, at least on my fs), =20 bittorrents clients were generating as lot of disk as previously so I gues = =20 it's more likely coused by data/tree fragmentation. Just my 0,6374526$ ;)