Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Little\s+questions\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Little\s+questions\s*$/: 23 ]

Total 23 documents matching your query.

21. Re: Little questions (score: 1): Author: yoros@xxxxxxxxxx; Date: Tue, 29 Oct 2002 23:30:18 +0100; When a file is very fragmented... ext2 only have to remove a few blocks (inode, simple-indirect, double-indirect, etc...). This is the historic Tanembaum's standard and a lot of UNIX-filesystems impl; /archives/xfs/2002-10/msg02253.html (9,162 bytes)
22. Re: Little questions (score: 1): Author: Stephen Lord <lord@xxxxxxx>; Date: 29 Oct 2002 17:03:53 -0600; for every block in the file ext2 needs to free this block and place it in the bitmaps. For xfs the same is true, it needs to free each extent. One of the issues with a journalled filesystem is we nee; /archives/xfs/2002-10/msg02254.html (9,807 bytes)
23. Re: Little questions (score: 1): Author: yoros@xxxxxxxxxx; Date: Wed, 30 Oct 2002 06:11:02 +0100; Yes, I understand that removing a file with more than 40000 extents takes a LOT of time and that is not bad because such file has too much extents. What structure is created for each extent? This is; /archives/xfs/2002-10/msg02262.html (11,116 bytes)

Current List: 21 - 23
Page: [1] [2]