Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*low\s+level\s+access\s+path\s+for\s+xfs\s+operation\s*$/: 12 ]

Total 12 documents matching your query.

1. low level access path for xfs operation (score: 1)
Author: Soon-Son Kwon <kss@xxxxxxxx>
Date: Fri, 21 Mar 2003 12:40:47 +0900
Hi xfs folks: Could anyone please let me know the following xfs internal operation details? I would like to know if there is any operation that bypasses submit_bio() when accessing the lower level bl
/archives/xfs/2003-03/msg00295.html (8,366 bytes)

2. Re: low level access path for xfs operation (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Fri, 21 Mar 2003 09:14:23 +0000
No, there is no such operation. You might want to rewrite a block remapper like dm or md instead of modifying core core..
/archives/xfs/2003-03/msg00298.html (8,410 bytes)

3. Re: low level access path for xfs operation (score: 1)
Author: Soon-Son Kwon <kss@xxxxxxxx>
Date: Fri, 21 Mar 2003 19:43:53 +0900
What I would like to implement is the snapshot functionality within the filesystem. I know LVM supports snapshot but it requires a separate volume for each snapshot. I thought snapshot within the fil
/archives/xfs/2003-03/msg00299.html (10,027 bytes)

4. Re: low level access path for xfs operation (score: 1)
Author: Chris Wedgwood <cw@xxxxxxxx>
Date: Fri, 21 Mar 2003 12:40:52 -0800
How should this work from a user perspective? You need to be sure whatever mechanism you use to keep track of block placements is efficient and the granularity are sane or else the metadata to keep t
/archives/xfs/2003-03/msg00304.html (9,188 bytes)

5. Re: low level access path for xfs operation (score: 1)
Author: Soon-Son Kwon <kss@xxxxxxxx>
Date: Sat, 22 Mar 2003 10:14:27 +0900
If a snapshot can be generated/maintained within the filesystem, the user do not have to care for the overall disk layout as long as there are some free spaces in the filesystem while LVM requires ad
/archives/xfs/2003-03/msg00310.html (11,708 bytes)

6. Re: low level access path for xfs operation (score: 1)
Author: Jeremy Jackson <jerj@xxxxxxxxxxxx>
Date: 25 Mar 2003 09:30:38 -0500
If using EVMS with dm/LVM, it is easy to make another volume. The administrator needs to learn the hard way not to fill up the disk with a filesystem that cannot shrink. (I know I have) It will creat
/archives/xfs/2003-03/msg00331.html (12,268 bytes)

7. low level access path for xfs operation (score: 1)
Author: Soon-Son Kwon <kss@xxxxxxxx>
Date: Fri, 21 Mar 2003 12:40:47 +0900
Hi xfs folks: Could anyone please let me know the following xfs internal operation details? I would like to know if there is any operation that bypasses submit_bio() when accessing the lower level bl
/archives/xfs/2003-03/msg00764.html (8,366 bytes)

8. Re: low level access path for xfs operation (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Fri, 21 Mar 2003 09:14:23 +0000
No, there is no such operation. You might want to rewrite a block remapper like dm or md instead of modifying core core..
/archives/xfs/2003-03/msg00767.html (8,410 bytes)

9. Re: low level access path for xfs operation (score: 1)
Author: Soon-Son Kwon <kss@xxxxxxxx>
Date: Fri, 21 Mar 2003 19:43:53 +0900
What I would like to implement is the snapshot functionality within the filesystem. I know LVM supports snapshot but it requires a separate volume for each snapshot. I thought snapshot within the fil
/archives/xfs/2003-03/msg00768.html (10,027 bytes)

10. Re: low level access path for xfs operation (score: 1)
Author: Chris Wedgwood <cw@xxxxxxxx>
Date: Fri, 21 Mar 2003 12:40:52 -0800
How should this work from a user perspective? You need to be sure whatever mechanism you use to keep track of block placements is efficient and the granularity are sane or else the metadata to keep t
/archives/xfs/2003-03/msg00773.html (9,188 bytes)

11. Re: low level access path for xfs operation (score: 1)
Author: Soon-Son Kwon <kss@xxxxxxxx>
Date: Sat, 22 Mar 2003 10:14:27 +0900
If a snapshot can be generated/maintained within the filesystem, the user do not have to care for the overall disk layout as long as there are some free spaces in the filesystem while LVM requires ad
/archives/xfs/2003-03/msg00779.html (11,708 bytes)

12. Re: low level access path for xfs operation (score: 1)
Author: Jeremy Jackson <jerj@xxxxxxxxxxxx>
Date: 25 Mar 2003 09:30:38 -0500
If using EVMS with dm/LVM, it is easy to make another volume. The administrator needs to learn the hard way not to fill up the disk with a filesystem that cannot shrink. (I know I have) It will creat
/archives/xfs/2003-03/msg00800.html (12,268 bytes)


This search system is powered by Namazu