Hi.
On Fri, Feb 01, 2008 at 02:04:39AM +0100, Jan Engelhardt ([EMAIL PROTECTED])
wrote:
> >POHMELFS stands for Parallel Optimized Host Message Exchange
> >Layered File System. It allows to mount remote servers to local
> >directory via network. This filesystem supports local caching
> >and writeb
Sato-san,
> > What you *could* do is to start putting processes to sleep if they
> > attempt to write to the frozen filesystem, and then detect the
> > deadlock case where the process holding the file descriptor used to
> > freeze the filesystem gets frozen because it attempted to write to the
>
On Jan 31 2008 22:17, Evgeniy Polyakov wrote:
>
>POHMELFS stands for Parallel Optimized Host Message Exchange
>Layered File System. It allows to mount remote servers to local
>directory via network. This filesystem supports local caching
>and writeback flushing.
>POHMELFS is a brick in a future di
Chuck Lever <[EMAIL PROTECTED]> wrote:
> >>> +struct nfs_fh_auxdata {
> >>> + struct timespec i_mtime;
> >>> + struct timespec i_ctime;
> >>> + loff_t i_size;
> >>> +};
> >>
> >> It might be useful to explain here why you need to supplement the
> >> mtime, ctime, and size fields that alre
This patch disables writeback in POHMELFS and creates all objects
on behalf of its own without sync with remote side.
This mode is _very_ fast.
If POHEMLFS would be bound to single remote filesystem, it could
use its inode allocation policy and be very happy with write-back cache.
By design POHMEL
Hi.
POHMELFS stands for Parallel Optimized Host Message Exchange
Layered File System. It allows to mount remote servers to local
directory via network. This filesystem supports local caching
and writeback flushing.
POHMELFS is a brick in a future distributed filesystem.
This set includes two patc
On Thu, 2008-01-31 at 10:17 +0100, Miklos Szeredi wrote:
> > > From: Ram Pai <[EMAIL PROTECTED]>
...snipped...
> IDR ids are 'int' but they are always positive (AFAICT), but yeah,
> maybe this is confusing.
>
> > The new exported-to-everyone dentry_path() probably could do with a bit
> > more do
> > > - loop: how is the connection between file and loop device maintained?
> >
> > We also discussed this with Karel, maybe it didn't make it onto lkml.
> >
> > The proposed solution was to store the "loop" flag separately in a
> > file under /var. It could just be an empty file for each such
On Thursday 31 January 2008, Jan Kara wrote:
> On Thu 31-01-08 11:56:01, Chris Mason wrote:
> > On Thursday 31 January 2008, Al Boldi wrote:
> > > Andreas Dilger wrote:
> > > > On Wednesday 30 January 2008, Al Boldi wrote:
> > > > > And, a quick test of successive 1sec delayed syncs shows no hangs
On Thu 31-01-08 11:56:01, Chris Mason wrote:
> On Thursday 31 January 2008, Al Boldi wrote:
> > Andreas Dilger wrote:
> > > On Wednesday 30 January 2008, Al Boldi wrote:
> > > > And, a quick test of successive 1sec delayed syncs shows no hangs until
> > > > about 1 minute (~180mb) of db-writeout ac
On Thursday 31 January 2008, Al Boldi wrote:
> Andreas Dilger wrote:
> > On Wednesday 30 January 2008, Al Boldi wrote:
> > > And, a quick test of successive 1sec delayed syncs shows no hangs until
> > > about 1 minute (~180mb) of db-writeout activity, when the sync abruptly
> > > hangs for minutes
Hi.
I managed to get following circular locking bug during fs development.
I can not reproduce it and it was caught during another fs development,
so that can be related, but as is it looks like a bug.
Hope this helps:
===
[ INFO: possible circ
On Thu, 2008-01-31 at 10:46 +0100, Miklos Szeredi wrote:
> > On Tue, 29 Jan 2008 16:49:06 +0100
> > Miklos Szeredi <[EMAIL PROTECTED]> wrote:
> >
> > > Add "max_ratio" to /sys/class/bdi. This indicates the maximum
> > > percentage of the global dirty threshold allocated to this bdi.
> >
> > May
On Thu, 2008-01-31 at 01:54 -0800, Andrew Morton wrote:
> On Thu, 31 Jan 2008 10:39:02 +0100 Miklos Szeredi <[EMAIL PROTECTED]> wrote:
>
> > > On Tue, 29 Jan 2008 16:49:02 +0100
> > > Miklos Szeredi <[EMAIL PROTECTED]> wrote:
> > >
> > > > From: Peter Zijlstra <[EMAIL PROTECTED]>
> > > >
> > >
On Thu, 31 Jan 2008 10:39:02 +0100 Miklos Szeredi <[EMAIL PROTECTED]> wrote:
> > On Tue, 29 Jan 2008 16:49:02 +0100
> > Miklos Szeredi <[EMAIL PROTECTED]> wrote:
> >
> > > From: Peter Zijlstra <[EMAIL PROTECTED]>
> > >
> > > Provide a place in sysfs (/sys/class/bdi) for the backing_dev_info
> >
> On Tue, 29 Jan 2008 16:49:06 +0100
> Miklos Szeredi <[EMAIL PROTECTED]> wrote:
>
> > Add "max_ratio" to /sys/class/bdi. This indicates the maximum
> > percentage of the global dirty threshold allocated to this bdi.
>
> Maybe I'm having a stupid day, but I don't understand the semantics of this
> On Tue, 29 Jan 2008 16:49:02 +0100
> Miklos Szeredi <[EMAIL PROTECTED]> wrote:
>
> > From: Peter Zijlstra <[EMAIL PROTECTED]>
> >
> > Provide a place in sysfs (/sys/class/bdi) for the backing_dev_info
> > object. This allows us to see and set the various BDI specific
> > variables.
> >
> > In
> > From: Ram Pai <[EMAIL PROTECTED]>
> >
> > /proc/mounts in its current state fails to disambiguate bind mounts,
> > especially when the bind mount is subrooted. Also it does not capture
> > propagation state of the mounts(shared-subtree). The following patch
> > addresses the problem.
> >
>
On Friday 25 January 2008 05:33, Theodore Tso wrote:
> and then detect the
> deadlock case where the process holding the file descriptor used to
> freeze the filesystem gets frozen because it attempted to write to the
> filesystem --- at which point it gets some kind of signal (which
> defaults to
19 matches
Mail list logo
