| To: | "Gopala Krishna" <gopalakrishna.n.m@xxxxxxxxx> |
|---|---|
| Subject: | Re: Question related to XFS sync , especially fsync |
| From: | Andi Kleen <andi@xxxxxxxxxxxxxx> |
| Date: | Thu, 17 Jan 2008 02:25:00 +0100 |
| Cc: | "Chris Wedgwood" <cw@xxxxxxxx>, nscott@xxxxxxxxxx, xfs@xxxxxxxxxxx |
| In-reply-to: | <d711080c0801152325g3d57965dm92e3687a5f98c5f6@xxxxxxxxxxxxxx> (Gopala Krishna's message of "Wed\, 16 Jan 2008 12\:55\:17 +0530") |
| References: | <d711080c0801140414n48e47140y88f545eba605eff9@xxxxxxxxxxxxxx> <20080114224245.GT155259@xxxxxxx> <d711080c0801150544i53d7abb2hbea659116ce0006b@xxxxxxxxxxxxxx> <478CCEAC.9010008@xxxxxxxxxxx> <1200436012.9463.184.camel@xxxxxxxxxxxxxxxxx> <d711080c0801152243h7613bbean9daeab8658f75408@xxxxxxxxxxxxxx> <20080116064840.GA5725@xxxxxxxxxxxxxxxxxx> <d711080c0801152325g3d57965dm92e3687a5f98c5f6@xxxxxxxxxxxxxx> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux) |
"Gopala Krishna" <gopalakrishna.n.m@xxxxxxxxx> writes: > we need to get information about > file like it's extent information and associated block numbers etc. To > extract these there is no system call Actually there is the FIOBMAP ioctl for data blocks. e.g. it's used by boot loaders like lilo to create a block map to read a file without knowledge of the file system. Should work on all file systems that support lilo. It won't give you information about metadata blocks though. -Andi |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Question related to XFS sync , especially fsync, Mark Goodwin |
|---|---|
| Next by Date: | Re: Repairing a possibly incomplete xfs_growfs command?, Eric Sandeen |
| Previous by Thread: | Re: Question related to XFS sync , especially fsync, Mark Goodwin |
| Next by Thread: | Re: Question related to XFS sync , especially fsync, David Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |