All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Popelka <jpopelka@redhat.com>
To: Michael Sweet <msweet@apple.com>
Cc: printing-architecture@lists.linux-foundation.org,
	sandeen@redhat.com, sbergman27@gmail.com
Subject: [Printing-architecture] printers.conf frequently gets truncated to zero length after unclean shutdowns
Date: Mon, 22 Jul 2013 19:28:58 +0200	[thread overview]
Message-ID: <51ED6BDA.2080206@redhat.com> (raw)

Hello,

When cupsd lives on a filesystem with delayed allocation, like ext4 and
it experience an unclean shutdown under heavy load, its printers.conf 
very often ends up being truncated to zero.

Even original report (https://bugzilla.redhat.com/show_bug.cgi?id=984883)
has been against cups-1.4.2 I've seen no reason to think this has been 
fixed in recent versions.
I see cupsd since 1.5 (due to STR #3715) has been more carefully 
creating and removing conf files,
but that doesn't seem to be sufficient.
Especially updating of printers.conf probably needs some sort of 
synchronization data to disk.

I have a patch (in comment #11), which makes cupsd read backup 
filename.O file if filename is truncated to zero, but that's only a 
work-around
and I'm afraid it won't work if the file gets updated couple times 
between last sync and the unexpected shutdown.

I've promised interested parties to ask you publicly
and since bug tracker @ cups.org is still down ... here I am ;-)

With regards,
Jiri

             reply	other threads:[~2013-07-22 17:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-22 17:28 Jiri Popelka [this message]
2013-07-22 17:46 ` [Printing-architecture] printers.conf frequently gets truncated to zero length after unclean shutdowns Till Kamppeter
     [not found]   ` <51EDADB4.5000807@redhat.com>
2013-07-23  3:03     ` Michael Sweet
     [not found] ` <51ED6CC4.1040501@redhat.com>
2013-07-23  3:00   ` Michael Sweet
2013-07-23  9:08     ` Tim Waugh
2013-07-23 12:08       ` Michael Sweet
     [not found]         ` <51EE90D7.9070607@gmail.com>
2013-07-23 16:40           ` Michael Sweet
     [not found]             ` <51EEBF83.2090006@gmail.com>
2013-07-23 18:16               ` Michael Sweet
     [not found]                 ` <51EECB0D.5050208@redhat.com>
2013-07-23 18:59                   ` Michael Sweet
     [not found]                 ` <51EECDF8.9070209@gmail.com>
2013-07-23 19:01                   ` Michael Sweet
2013-07-23 20:51                     ` Till Kamppeter
2013-07-23 23:04                       ` Michael R Sweet
2013-07-24 10:11                       ` Jiri Popelka
2013-07-24 11:39                         ` Michael Sweet
2013-07-26 21:36                     ` Michael Sweet
     [not found]                       ` <51F2F05E.3000207@redhat.com>
2013-07-26 22:10                         ` Michael Sweet
     [not found]     ` <51EE1183.5080704@redhat.com>
2013-07-23 12:05       ` Michael Sweet
     [not found]         ` <51EEA872.4070009@redhat.com>
2013-07-23 17:51           ` Michael Sweet

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51ED6BDA.2080206@redhat.com \
    --to=jpopelka@redhat.com \
    --cc=msweet@apple.com \
    --cc=printing-architecture@lists.linux-foundation.org \
    --cc=sandeen@redhat.com \
    --cc=sbergman27@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.