| To: | xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Question on migrating data between PVs in xfs |
| From: | Wei Lin <lin.wei15@xxxxxxxxxxxxxx> |
| Date: | Tue, 9 Aug 2016 15:50:47 +0100 |
| Delivered-to: | xfs@xxxxxxxxxxx |
| Dkim-signature: | v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=imperial.ac.uk; s=main01; h=Content-Type:MIME-Version:Message-ID:Subject:To :From:Date; bh=QSGCZVaJ2M9bV/g9i2qnyiU4h7AmHRypDsQ6+3QAdI0=; b=Ug7L+oBIp4Tw8Y tuEB3FC28egGKz/pNoAcmEX44H56WLJJ1VjvWfEsy923coSkuBaJGrUEWswP8Yu4f00+cwkfADc6q VoiBHz7ViEGHbauM6boWJsOABrRrq6mQLShLEG8OBeNogNpNvpTyqbNCk5motbIi256saLtpaEVAC LBU=; |
| User-agent: | Mutt/1.6.2 (2016-07-01) |
Hi there, I am working on an xfs based project and want to modify the allocation algorithm, which is quite involved. I am wondering if anyone could help with this. The high level goal is to create xfs agains multiple physical volumes, allow user to specify the target PV for files, and migrate files automatically. I plan to implement the user interface with extended attributes, but am now stuck with the allocation/migration part. Is there a way to make xfs respect the attribute, i.e. only allocate blocks/extents from the target PV specified by user? Any suggestion would be highly appreciated. Cheers, -- Wei Lin |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [PATCH xfsprogs] libxcmd: link against used libs, Mike Frysinger |
|---|---|
| Next by Date: | Vacaciona en Puerto Vallarta, Franco Aros |
| Previous by Thread: | [PATCH xfsprogs] libxcmd: link against used libs, Mike Frysinger |
| Next by Thread: | Re: Question on migrating data between PVs in xfs, Dave Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |