Hi.
Pavel Machek wrote:
> On Fri 2008-01-04 21:54:06, Oliver Neukum wrote:
>> Am Donnerstag, 3. Januar 2008 23:06:07 schrieb Nigel Cunningham:
>>> Oliver Neukum wrote:
Am Donnerstag, 3. Januar 2008 10:52:53 schrieb Nigel Cunningham:
> Oliver Neukum wrote:
>> Am Donnerstag 03 Januar
On Fri 2008-01-04 21:54:06, Oliver Neukum wrote:
> Am Donnerstag, 3. Januar 2008 23:06:07 schrieb Nigel Cunningham:
> > Hi.
> >
> > Oliver Neukum wrote:
> > > Am Donnerstag, 3. Januar 2008 10:52:53 schrieb Nigel Cunningham:
> > >> Hi.
> > >>
> > >> Oliver Neukum wrote:
> > >>> Am Donnerstag 03
On Fri 2008-01-04 21:54:06, Oliver Neukum wrote:
Am Donnerstag, 3. Januar 2008 23:06:07 schrieb Nigel Cunningham:
Hi.
Oliver Neukum wrote:
Am Donnerstag, 3. Januar 2008 10:52:53 schrieb Nigel Cunningham:
Hi.
Oliver Neukum wrote:
Am Donnerstag 03 Januar 2008 schrieb Nigel
Hi.
Pavel Machek wrote:
On Fri 2008-01-04 21:54:06, Oliver Neukum wrote:
Am Donnerstag, 3. Januar 2008 23:06:07 schrieb Nigel Cunningham:
Oliver Neukum wrote:
Am Donnerstag, 3. Januar 2008 10:52:53 schrieb Nigel Cunningham:
Oliver Neukum wrote:
Am Donnerstag 03 Januar 2008 schrieb Nigel
On Jan 04, 2008, at 15:54:06, Oliver Neukum wrote:
Am Donnerstag, 3. Januar 2008 23:06:07 schrieb Nigel Cunningham:
Hi.
a) mount fuse on /tmp/first
b) mount fuse on /tmp/second
Then the server task for (a) does "ls /tmp/second". So it will be
frozen, right? How do you then freeze (a)? And
Am Donnerstag, 3. Januar 2008 23:06:07 schrieb Nigel Cunningham:
> Hi.
>
> Oliver Neukum wrote:
> > Am Donnerstag, 3. Januar 2008 10:52:53 schrieb Nigel Cunningham:
> >> Hi.
> >>
> >> Oliver Neukum wrote:
> >>> Am Donnerstag 03 Januar 2008 schrieb Nigel Cunningham:
> On top of this, I made a
Am Donnerstag, 3. Januar 2008 23:06:07 schrieb Nigel Cunningham:
Hi.
Oliver Neukum wrote:
Am Donnerstag, 3. Januar 2008 10:52:53 schrieb Nigel Cunningham:
Hi.
Oliver Neukum wrote:
Am Donnerstag 03 Januar 2008 schrieb Nigel Cunningham:
On top of this, I made a (too simple at the
On Jan 04, 2008, at 15:54:06, Oliver Neukum wrote:
Am Donnerstag, 3. Januar 2008 23:06:07 schrieb Nigel Cunningham:
Hi.
a) mount fuse on /tmp/first
b) mount fuse on /tmp/second
Then the server task for (a) does ls /tmp/second. So it will be
frozen, right? How do you then freeze (a)? And
On Thursday, 3 of January 2008, Nigel Cunningham wrote:
> Hi.
>
> Rafael J. Wysocki wrote:
> > On Wednesday, 2 of January 2008, Nigel Cunningham wrote:
> >> Pavel Machek wrote:
> So how do you handle threads that are blocked on I/O or a lock
> during the system freeze process,
Hi.
Oliver Neukum wrote:
> Am Donnerstag, 3. Januar 2008 10:52:53 schrieb Nigel Cunningham:
>> Hi.
>>
>> Oliver Neukum wrote:
>>> Am Donnerstag 03 Januar 2008 schrieb Nigel Cunningham:
On top of this, I made a (too simple at the moment) freeze_filesystems
function which iterates through
Am Donnerstag, 3. Januar 2008 10:52:53 schrieb Nigel Cunningham:
> Hi.
>
> Oliver Neukum wrote:
> > Am Donnerstag 03 Januar 2008 schrieb Nigel Cunningham:
> >> On top of this, I made a (too simple at the moment) freeze_filesystems
> >> function which iterates through _blocks in reverse order,
Hi.
Oliver Neukum wrote:
> Am Donnerstag 03 Januar 2008 schrieb Nigel Cunningham:
>> On top of this, I made a (too simple at the moment) freeze_filesystems
>> function which iterates through _blocks in reverse order, freezing
>> fuse filesystems or ordinary ones. I say 'too simple' because it
Am Donnerstag 03 Januar 2008 schrieb Nigel Cunningham:
> On top of this, I made a (too simple at the moment) freeze_filesystems
> function which iterates through _blocks in reverse order, freezing
> fuse filesystems or ordinary ones. I say 'too simple' because it doesn't
> currently allow for the
Hi.
Rafael J. Wysocki wrote:
> On Wednesday, 2 of January 2008, Nigel Cunningham wrote:
>> Pavel Machek wrote:
So how do you handle threads that are blocked on I/O or a lock
during the system freeze process, then?
>>> We wait until they can continue.
>> So if I have a
Hi.
Rafael J. Wysocki wrote:
On Wednesday, 2 of January 2008, Nigel Cunningham wrote:
Pavel Machek wrote:
So how do you handle threads that are blocked on I/O or a lock
during the system freeze process, then?
We wait until they can continue.
So if I have a process blocked on an unavilable
Am Donnerstag 03 Januar 2008 schrieb Nigel Cunningham:
On top of this, I made a (too simple at the moment) freeze_filesystems
function which iterates through super_blocks in reverse order, freezing
fuse filesystems or ordinary ones. I say 'too simple' because it doesn't
currently allow for the
Hi.
Oliver Neukum wrote:
Am Donnerstag 03 Januar 2008 schrieb Nigel Cunningham:
On top of this, I made a (too simple at the moment) freeze_filesystems
function which iterates through super_blocks in reverse order, freezing
fuse filesystems or ordinary ones. I say 'too simple' because it
Am Donnerstag, 3. Januar 2008 10:52:53 schrieb Nigel Cunningham:
Hi.
Oliver Neukum wrote:
Am Donnerstag 03 Januar 2008 schrieb Nigel Cunningham:
On top of this, I made a (too simple at the moment) freeze_filesystems
function which iterates through super_blocks in reverse order, freezing
Hi.
Oliver Neukum wrote:
Am Donnerstag, 3. Januar 2008 10:52:53 schrieb Nigel Cunningham:
Hi.
Oliver Neukum wrote:
Am Donnerstag 03 Januar 2008 schrieb Nigel Cunningham:
On top of this, I made a (too simple at the moment) freeze_filesystems
function which iterates through super_blocks in
On Thursday, 3 of January 2008, Nigel Cunningham wrote:
Hi.
Rafael J. Wysocki wrote:
On Wednesday, 2 of January 2008, Nigel Cunningham wrote:
Pavel Machek wrote:
So how do you handle threads that are blocked on I/O or a lock
during the system freeze process, then?
We wait until
On Wednesday, 2 of January 2008, Nigel Cunningham wrote:
> Hi.
>
> Pavel Machek wrote:
> > Hi!
> >
> >> So how do you handle threads that are blocked on I/O or a lock
> >> during the system freeze process, then?
> > We wait until they can continue.
> So if I have a process
Hi.
Pavel Machek wrote:
> Hi!
>
>> So how do you handle threads that are blocked on I/O or a lock
>> during the system freeze process, then?
> We wait until they can continue.
So if I have a process blocked on an unavilable NFS mount, I can't
suspend?
>>> That's correct,
Hi!
> So how do you handle threads that are blocked on I/O or a lock
> during the system freeze process, then?
> >>>
> >>>We wait until they can continue.
> >>
> >>So if I have a process blocked on an unavilable NFS mount, I can't
> >>suspend?
> >
> >That's correct, you can't.
> >
>
Hi!
So how do you handle threads that are blocked on I/O or a lock
during the system freeze process, then?
We wait until they can continue.
So if I have a process blocked on an unavilable NFS mount, I can't
suspend?
That's correct, you can't.
[And I know what you're going to say.
Hi.
Pavel Machek wrote:
Hi!
So how do you handle threads that are blocked on I/O or a lock
during the system freeze process, then?
We wait until they can continue.
So if I have a process blocked on an unavilable NFS mount, I can't
suspend?
That's correct, you can't.
[And I know what
On Wednesday, 2 of January 2008, Nigel Cunningham wrote:
Hi.
Pavel Machek wrote:
Hi!
So how do you handle threads that are blocked on I/O or a lock
during the system freeze process, then?
We wait until they can continue.
So if I have a process blocked on an unavilable NFS mount,
Kyle Moffett wrote:
> On Nov 27, 2007, at 17:49:18, Jeremy Fitzhardinge wrote:
>> Rafael J. Wysocki wrote:
>>> Well, this is more-or-less how we all imagine that should be done
>>> eventually.
>>>
>>> The main problem is how to implement it without causing too much
>>> breakage. Also, there are
On Nov 27, 2007, at 17:49:18, Jeremy Fitzhardinge wrote:
Rafael J. Wysocki wrote:
Well, this is more-or-less how we all imagine that should be done
eventually.
The main problem is how to implement it without causing too much
breakage. Also, there are some dirty details that need to be
Rafael J. Wysocki wrote:
> Well, this is more-or-less how we all imagine that should be done eventually.
>
> The main problem is how to implement it without causing too much breakage.
> Also, there are some dirty details that need to be taken into consideration.
>
For Xen suspend/resume, I'd
On Tuesday, 27 of November 2007, Kyle Moffett wrote:
> On Nov 27, 2007, at 12:40:24, Rafael J. Wysocki wrote:
> > On Tuesday, 27 of November 2007, Matthew Garrett wrote:
> >> On Mon, Nov 26, 2007 at 10:53:34PM +0100, Rafael J. Wysocki wrote:
> >>> On Monday, 26 of November 2007, David Chinner
On Nov 27, 2007, at 12:40:24, Rafael J. Wysocki wrote:
On Tuesday, 27 of November 2007, Matthew Garrett wrote:
On Mon, Nov 26, 2007 at 10:53:34PM +0100, Rafael J. Wysocki wrote:
On Monday, 26 of November 2007, David Chinner wrote:
So how do you handle threads that are blocked on I/O or a lock
On Tuesday, 27 of November 2007, Matthew Garrett wrote:
> On Mon, Nov 26, 2007 at 10:53:34PM +0100, Rafael J. Wysocki wrote:
> > On Monday, 26 of November 2007, David Chinner wrote:
> > > So how do you handle threads that are blocked on I/O or a lock during
> > > the system freeze process, then?
>
On Tuesday, 27 of November 2007, Matthew Garrett wrote:
On Mon, Nov 26, 2007 at 10:53:34PM +0100, Rafael J. Wysocki wrote:
On Monday, 26 of November 2007, David Chinner wrote:
So how do you handle threads that are blocked on I/O or a lock during
the system freeze process, then?
We
On Nov 27, 2007, at 12:40:24, Rafael J. Wysocki wrote:
On Tuesday, 27 of November 2007, Matthew Garrett wrote:
On Mon, Nov 26, 2007 at 10:53:34PM +0100, Rafael J. Wysocki wrote:
On Monday, 26 of November 2007, David Chinner wrote:
So how do you handle threads that are blocked on I/O or a lock
On Tuesday, 27 of November 2007, Kyle Moffett wrote:
On Nov 27, 2007, at 12:40:24, Rafael J. Wysocki wrote:
On Tuesday, 27 of November 2007, Matthew Garrett wrote:
On Mon, Nov 26, 2007 at 10:53:34PM +0100, Rafael J. Wysocki wrote:
On Monday, 26 of November 2007, David Chinner wrote:
So
Rafael J. Wysocki wrote:
Well, this is more-or-less how we all imagine that should be done eventually.
The main problem is how to implement it without causing too much breakage.
Also, there are some dirty details that need to be taken into consideration.
For Xen suspend/resume, I'd like
On Nov 27, 2007, at 17:49:18, Jeremy Fitzhardinge wrote:
Rafael J. Wysocki wrote:
Well, this is more-or-less how we all imagine that should be done
eventually.
The main problem is how to implement it without causing too much
breakage. Also, there are some dirty details that need to be
Kyle Moffett wrote:
On Nov 27, 2007, at 17:49:18, Jeremy Fitzhardinge wrote:
Rafael J. Wysocki wrote:
Well, this is more-or-less how we all imagine that should be done
eventually.
The main problem is how to implement it without causing too much
breakage. Also, there are some dirty details
On Mon, Nov 26, 2007 at 10:53:34PM +0100, Rafael J. Wysocki wrote:
> On Monday, 26 of November 2007, David Chinner wrote:
> > So how do you handle threads that are blocked on I/O or a lock during
> > the system freeze process, then?
>
> We wait until they can continue.
So if I have a process
On Monday, 26 of November 2007, David Chinner wrote:
> On Sat, Nov 24, 2007 at 12:47:21AM +0100, Rafael J. Wysocki wrote:
> > On Thursday, 22 of November 2007, Jeremy Fitzhardinge wrote:
> > > It seems that a process blocked in a write to an xfs filesystem due to
> > > xfs_freeze cannot be frozen
On Sat, Nov 24, 2007 at 12:47:21AM +0100, Rafael J. Wysocki wrote:
> On Thursday, 22 of November 2007, Jeremy Fitzhardinge wrote:
> > It seems that a process blocked in a write to an xfs filesystem due to
> > xfs_freeze cannot be frozen by the freezer.
>
> The freezer doesn't handle tasks in
On Monday, 26 of November 2007, Jeremy Fitzhardinge wrote:
> Rafael J. Wysocki wrote:
> > On Thursday, 22 of November 2007, Jeremy Fitzhardinge wrote:
> >
> >> It seems that a process blocked in a write to an xfs filesystem due to
> >> xfs_freeze cannot be frozen by the freezer.
> >>
> >
>
Rafael J. Wysocki wrote:
> On Thursday, 22 of November 2007, Jeremy Fitzhardinge wrote:
>
>> It seems that a process blocked in a write to an xfs filesystem due to
>> xfs_freeze cannot be frozen by the freezer.
>>
>
> The freezer doesn't handle tasks in TASK_UNINTERRUPTIBLE and I don't
Rafael J. Wysocki wrote:
On Thursday, 22 of November 2007, Jeremy Fitzhardinge wrote:
It seems that a process blocked in a write to an xfs filesystem due to
xfs_freeze cannot be frozen by the freezer.
The freezer doesn't handle tasks in TASK_UNINTERRUPTIBLE and I don't know how
to
On Monday, 26 of November 2007, Jeremy Fitzhardinge wrote:
Rafael J. Wysocki wrote:
On Thursday, 22 of November 2007, Jeremy Fitzhardinge wrote:
It seems that a process blocked in a write to an xfs filesystem due to
xfs_freeze cannot be frozen by the freezer.
The freezer
On Sat, Nov 24, 2007 at 12:47:21AM +0100, Rafael J. Wysocki wrote:
On Thursday, 22 of November 2007, Jeremy Fitzhardinge wrote:
It seems that a process blocked in a write to an xfs filesystem due to
xfs_freeze cannot be frozen by the freezer.
The freezer doesn't handle tasks in
On Monday, 26 of November 2007, David Chinner wrote:
On Sat, Nov 24, 2007 at 12:47:21AM +0100, Rafael J. Wysocki wrote:
On Thursday, 22 of November 2007, Jeremy Fitzhardinge wrote:
It seems that a process blocked in a write to an xfs filesystem due to
xfs_freeze cannot be frozen by the
On Mon, Nov 26, 2007 at 10:53:34PM +0100, Rafael J. Wysocki wrote:
On Monday, 26 of November 2007, David Chinner wrote:
So how do you handle threads that are blocked on I/O or a lock during
the system freeze process, then?
We wait until they can continue.
So if I have a process blocked on
On Thursday, 22 of November 2007, Jeremy Fitzhardinge wrote:
> It seems that a process blocked in a write to an xfs filesystem due to
> xfs_freeze cannot be frozen by the freezer.
The freezer doesn't handle tasks in TASK_UNINTERRUPTIBLE and I don't know how
to make it handle them without at least
On Thursday, 22 of November 2007, Jeremy Fitzhardinge wrote:
It seems that a process blocked in a write to an xfs filesystem due to
xfs_freeze cannot be frozen by the freezer.
The freezer doesn't handle tasks in TASK_UNINTERRUPTIBLE and I don't know how
to make it handle them without at least
It seems that a process blocked in a write to an xfs filesystem due to
xfs_freeze cannot be frozen by the freezer.
I see this if I suspend my laptop while doing something xfs-filesystem
intensive, like a kernel build. My suspend scripts freeze the XFS
filesystem (as Dave said I should), which
It seems that a process blocked in a write to an xfs filesystem due to
xfs_freeze cannot be frozen by the freezer.
I see this if I suspend my laptop while doing something xfs-filesystem
intensive, like a kernel build. My suspend scripts freeze the XFS
filesystem (as Dave said I should), which
52 matches
Mail list logo
