Hi Nathan
I can also confirm that this patch resolves an issue I am seeing
with re-aim-7 writing to xfs fs mounted on ramdisk, I was also
getting EAGAIN.
Thanks
Darren
On Thu, 10 Feb 2005, Nathan Scott wrote:
> On Wed, Feb 09, 2005 at 05:44:54PM +0300, Alexander Y. Fomichev wrote:
> > On
Hi Nathan
I can also confirm that this patch resolves an issue I am seeing
with re-aim-7 writing to xfs fs mounted on ramdisk, I was also
getting EAGAIN.
Thanks
Darren
On Thu, 10 Feb 2005, Nathan Scott wrote:
On Wed, Feb 09, 2005 at 05:44:54PM +0300, Alexander Y. Fomichev wrote:
On
On Thursday 10 February 2005 07:54, Nathan Scott wrote:
> On Wed, Feb 09, 2005 at 05:44:54PM +0300, Alexander Y. Fomichev wrote:
> > On Wednesday 09 February 2005 04:29, Nathan Scott wrote:
> > > Is that an O_SYNC write, do you know? Or a write to an inode
> > > with the sync flag set?
> >
> >
On Thursday 10 February 2005 07:54, Nathan Scott wrote:
On Wed, Feb 09, 2005 at 05:44:54PM +0300, Alexander Y. Fomichev wrote:
On Wednesday 09 February 2005 04:29, Nathan Scott wrote:
Is that an O_SYNC write, do you know? Or a write to an inode
with the sync flag set?
Yes, it is
On Wed, Feb 09, 2005 at 05:44:54PM +0300, Alexander Y. Fomichev wrote:
> On Wednesday 09 February 2005 04:29, Nathan Scott wrote:
> > Is that an O_SYNC write, do you know? Or a write to an inode
> > with the sync flag set?
>
> Yes, it is O_SYNC, as i can see from fcron sources, and, no, kernel
On Wednesday 09 February 2005 04:29, Nathan Scott wrote:
> On Tue, Feb 08, 2005 at 08:51:36PM +0300, Alexander Y. Fomichev wrote:
> > G' day
> >
> > It looks like XFS broken somewhere in 2.6.11-rc1,
> > sadly i can't sand "right" bugreport, some facts only.
> > Upgrade to 2.6.11-rc2 makes fcron
On Wednesday 09 February 2005 04:29, Nathan Scott wrote:
On Tue, Feb 08, 2005 at 08:51:36PM +0300, Alexander Y. Fomichev wrote:
G' day
It looks like XFS broken somewhere in 2.6.11-rc1,
sadly i can't sand right bugreport, some facts only.
Upgrade to 2.6.11-rc2 makes fcron non-working for
On Wed, Feb 09, 2005 at 05:44:54PM +0300, Alexander Y. Fomichev wrote:
On Wednesday 09 February 2005 04:29, Nathan Scott wrote:
Is that an O_SYNC write, do you know? Or a write to an inode
with the sync flag set?
Yes, it is O_SYNC, as i can see from fcron sources, and, no, kernel
OK,
On Tue, Feb 08, 2005 at 08:51:36PM +0300, Alexander Y. Fomichev wrote:
> G' day
>
> It looks like XFS broken somewhere in 2.6.11-rc1,
> sadly i can't sand "right" bugreport, some facts only.
> Upgrade to 2.6.11-rc2 makes fcron non-working for me in case of
> crontabs directory is placed on XFS
G' day
It looks like XFS broken somewhere in 2.6.11-rc1,
sadly i can't sand "right" bugreport, some facts only.
Upgrade to 2.6.11-rc2 makes fcron non-working for me in case of
crontabs directory is placed on XFS partition.
When i try to install new crontab fcrontab die with error:
"could not
G' day
It looks like XFS broken somewhere in 2.6.11-rc1,
sadly i can't sand right bugreport, some facts only.
Upgrade to 2.6.11-rc2 makes fcron non-working for me in case of
crontabs directory is placed on XFS partition.
When i try to install new crontab fcrontab die with error:
could not
On Tue, Feb 08, 2005 at 08:51:36PM +0300, Alexander Y. Fomichev wrote:
G' day
It looks like XFS broken somewhere in 2.6.11-rc1,
sadly i can't sand right bugreport, some facts only.
Upgrade to 2.6.11-rc2 makes fcron non-working for me in case of
crontabs directory is placed on XFS
12 matches
Mail list logo
