| To: | "Chris Wedgwood" <cw@xxxxxxxx> |
|---|---|
| Subject: | Re: Question related to XFS sync , especially fsync |
| From: | "Gopala Krishna" <gopalakrishna.n.m@xxxxxxxxx> |
| Date: | Wed, 16 Jan 2008 12:55:17 +0530 |
| Cc: | nscott@xxxxxxxxxx, xfs@xxxxxxxxxxx |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=JWuwTZzb5K2nZ0yPXxUwQ4Etx3ybq0XK2sGXJ4TUf4Q=; b=WQhmtrH7TDMKeYQBPsttByKOgIkPofuMWyLe8UnkhWOjhb/ZJZOzAEXY5oE08p9+ypW1+Zl6j8ObjnlaP9YZDZmldKEdnjJQBICI8giaiWnDepMCnxaxT6Upt43fZPk6BZ8bLtdehUP65YU5klZNATqKm2vwd9CE2zL5ig0gXyA= |
| Domainkey-signature: | a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=UQLy/70s4O/xFo7EcvLyCnRD+P3qHV6u4ui+Z6Ro4Ob2oGY5bzJ/lOnj+43yHb4g0LDykw2dVKhw9yG8Ld302w++EYLQX61kD/Decf+pVscC/D1aSUPFSDz1FjJrV1dTRyNbWyj9mRh9ZTGK8i2sDzUDJAJbSyVNV98LCbm1RS4= |
| In-reply-to: | <20080116064840.GA5725@xxxxxxxxxxxxxxxxxx> |
| References: | <d711080c0801140414n48e47140y88f545eba605eff9@xxxxxxxxxxxxxx> <20080114224245.GT155259@xxxxxxx> <d711080c0801150544i53d7abb2hbea659116ce0006b@xxxxxxxxxxxxxx> <478CCEAC.9010008@xxxxxxxxxxx> <1200436012.9463.184.camel@xxxxxxxxxxxxxxxxx> <d711080c0801152243h7613bbean9daeab8658f75408@xxxxxxxxxxxxxx> <20080116064840.GA5725@xxxxxxxxxxxxxxxxxx> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
Thank you Chris. While replying to Eric, I mentioned why we are doing that. We are basically providing interfaces to back up applications in a pure storage environment that deals with the back up at block level (sector level) and hence depending upon different file system, 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 and hence we are depending on disk layout published by file system vendors and the header file provided by them. If there is a user level system call to deal with the extent information etc, we can use , but many file system is not providing that. Basically if we give file it should eb in aposition to display metadata informations including extents and corresponding logical block numbers and device offsets. I have to do it programitically and hence if I have some system call rather than command, that would be helpful. Freeze/unfreeze is a command it seems right? Thanks, Gopal. On 1/16/08, Chris Wedgwood <cw@xxxxxxxx> wrote: > > On Wed, Jan 16, 2008 at 12:13:54PM +0530, Gopala Krishna wrote: > > > Is there any XFS call from user level to flush metadata for a given > > file or complete log to disk? > > like a said earlier, try freeze/unfreeze > > you've not explained what you're doing (well, why you're doing it) > > it sounds very problematic by design > [[HTML alternate version deleted]] |
| Previous by Date: | Re: Question related to XFS sync , especially fsync, Gopala Krishna |
|---|---|
| Next by Date: | Re: Question related to XFS sync , especially fsync, Iustin Pop |
| Previous by Thread: | Re: Question related to XFS sync , especially fsync, Gopala Krishna |
| Next by Thread: | Re: Question related to XFS sync , especially fsync, Iustin Pop |
| Indexes: | [Date] [Thread] [Top] [All Lists] |