On Tuesday, July 02, 2013 09:19:07 PM Shridhar Daithankar wrote:
On Tuesday, July 02, 2013 01:00:29 PM Duncan wrote:
But I'd still expect there to be some better performance steady state
after a few mounts gets the basic filesystem defragged. Tho if the
fileystem is heavily fragmented[2],
On Tuesday, July 02, 2013 01:00:29 PM Duncan wrote:
Just to be clear, your system, your call. I'd never /dream/ of
interfering with that due to the implications for my own system (which is
certainly highly customized even matched against a peer-group of other
gentoo installs =:^). That
Shridhar Daithankar posted on Mon, 01 Jul 2013 08:20:19 +0530 as
excerpted:
On Sunday, June 30, 2013 01:53:48 PM Garry T. Williams wrote:
[discussing fragmentation]
~/.kde/share/apps/nepomuk/repository/main/data/virtuosobackend
damn!
# filefrag soprano-virtuoso.db soprano-virtuoso.db:
On Monday, July 01, 2013 09:10:41 AM Duncan wrote:
But in general, how to find out most fragmented files and folders?
mouting with autodefrag is a serious degradation..
It is? AFAIK, all the autodefrag mount option does is scan files for
fragmentation as they are written and queue any
Hello,
I have 3 partitions with btrfs(/, /home and /data). All of them have following
mount options
noatime,space_cache,inode_cache,compress=lzo,defaults
Whenever there is a unclean shutdown(which happens a lot in my case), the next
reboot, system comes up relatively at the same speed but as
On 6-30-13 19:26:16 Shridhar Daithankar wrote:
Whenever there is a unclean shutdown(which happens a lot in my
case), the next reboot, system comes up relatively at the same speed
but as systemd is starting up daemons, the disk is continuously (and
unusally long) grinding.
[snip]
How can I
On 06/30/2013 06:53 PM, Garry T. Williams wrote:
On 6-30-13 19:26:16 Shridhar Daithankar wrote:
Whenever there is a unclean shutdown(which happens a lot in my
case), the next reboot, system comes up relatively at the same speed
but as systemd is starting up daemons, the disk is continuously
Hi,
I suspect this is, at least in part, related to severe fragmentation
in /home.
In his cause those issues are only present after an unclean shutdown -
whereas fragmentation would show its effect after every reboot.
Regards, Clemens
--
To unsubscribe from this list: send the line
Garry T. Williams posted on Sun, 30 Jun 2013 13:53:48 -0400 as excerpted:
I suspect this is, at least in part, related to severe fragmentation in
/home.
There are large files in these directories that are updated frequently
by various components of KDE and the Chrome browser. (Firefox has
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 30/06/13 10:53, Garry T. Williams wrote:
~/.cache/chromium/Default/Cache ~/.cache/chromium/Default/Media\ Cache
I've taken to making ~/.cache be tmpfs and all the apps have been fine
with that. It also meant I didn't have to worry about my btrfs
On Sunday, June 30, 2013 01:53:48 PM Garry T. Williams wrote:
I suspect this is, at least in part, related to severe fragmentation
in /home.
I don't think so. The problem I have described occur only before anybody logs
in to the system and /home being a separate partition, it is not the
11 matches
Mail list logo
