![](https://secure.gravatar.com/avatar/fd77a9387963da792ed91b5ab48b24ea.jpg?s=120&d=mm&r=g)
We're attempting to install mailman on our new server. It's been running happily on our old one for years. This server is running Oracle 9 RHEL Linux. It uses postfix for its MTA. We built mailman 2. 1.39 from source, with the options ./configure --with-cgi-gid=apache –with-mail-gid=nobody . If someone subscribes to our mailing list, mailman will successfully send a confirmation message. Messages posted to the list, however, fail with:
Command died with status 1: "/usr/local/mailman/mail/mailman post newsletter". Command output: Traceback (most recent call last): File "/usr/local/mailman/scripts/post", line 69, in <module> main() File "/usr/local/mailman/scripts/post", line 64, in main tolist=1, _plaintext=1) File "/usr/local/mailman/Mailman/Queue/Switchboard.py", line 136, in enqueue fp = open(tmpfile, 'w') IOError: [Errno 30] Read-only file system: '/usr/local/mailman/qfiles/in/1719765141.057583+cb104828efdd0023821ead337d3d60f72e949690.pck.tmp'
Setting /usr/local/mailman/qfiles/in/ to have write permissions for all didn’t fix the problem. Does anyone have any experience with this issue, and a suggestion as to how to resolve it? We’ve tried everything we can think of, and madness is setting in. Thanks.
![](https://secure.gravatar.com/avatar/dbf97c196d6ec08d02e175372aecc411.jpg?s=120&d=mm&r=g)
On 6/30/24 19:27, John wrote:
Does anyone have any experience with this issue, and a suggestion as to how to resolve it? We’ve tried everything we can think of, and madness is setting in.
What are you running on? "Read-only filesystem" with shell looking like
everything's fine happens on dead drives and (more often) messed-up VM
storage volumes. "Read-only" bit doesn't eve show up in mount
when
that happens, as I recall.
Dima
![](https://secure.gravatar.com/avatar/56f108518d7ee2544412cc80978e3182.jpg?s=120&d=mm&r=g)
On 6/30/24 17:27, John wrote:
It is not clear what directory is the mount pount for this, but it is mounted read-only. No one, not even root, can write to it. Look at /etc/fstab
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
![](https://secure.gravatar.com/avatar/19e21a1f005c894a5543a086c1076e60.jpg?s=120&d=mm&r=g)
At Mon, 1 Jul 2024 12:45:11 -0700 Mark Sapiro <mark@msapiro.net> wrote:
If there was some sort of error, the file system would automatically be re-mounted read-only. Something like a power glitch, etc. can do this. Also a failing disk (sudden bad sector reads or writes).
-- Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364 Deepwoods Software -- Custom Software Services http://www.deepsoft.com/ -- Linux Administration Services heller@deepsoft.com -- Webhosting Services
![](https://secure.gravatar.com/avatar/1351fb866e8d35cad87c69e8b4c378bd.jpg?s=120&d=mm&r=g)
Yes a disk "failure" is possible,
I recently had a Samsung 980 pro nvme drive runout of spare blocks (due to bad firmware), this made the file system readonly.
Run smartctl on the disk(s) to check.
regards
Steven
From: Robert Heller <heller@deepsoft.com> Sent: Tuesday, 2 July 2024 8:21 am To: Mark Sapiro <mark@msapiro.net> Cc: mailman-users@python.org <mailman-users@python.org> Subject: [Mailman-Users] Re: Read-only file system
At Mon, 1 Jul 2024 12:45:11 -0700 Mark Sapiro <mark@msapiro.net> wrote:
If there was some sort of error, the file system would automatically be re-mounted read-only. Something like a power glitch, etc. can do this. Also a failing disk (sudden bad sector reads or writes).
-- Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364 Deepwoods Software -- Custom Software Services https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.deepsoft.com%2F&data=05%7C02%7Csteven.jones%40vuw.ac.nz%7C854ca3d22ee94fee6d9808dc9a0cd701%7Ccfe63e236951427e8683bb84dcf1d20c%7C0%7C0%7C638554627167864182%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=qm4l7rMm9RxwLTB%2FT%2FtTqj7Iswnbn4nIiPsm5pqRCnY%3D&reserved=0<http://www.deepsoft.com/> -- Linux Administration Services heller@deepsoft.com -- Webhosting Services
![](https://secure.gravatar.com/avatar/dbf97c196d6ec08d02e175372aecc411.jpg?s=120&d=mm&r=g)
On 6/30/24 19:27, John wrote:
Does anyone have any experience with this issue, and a suggestion as to how to resolve it? We’ve tried everything we can think of, and madness is setting in.
What are you running on? "Read-only filesystem" with shell looking like
everything's fine happens on dead drives and (more often) messed-up VM
storage volumes. "Read-only" bit doesn't eve show up in mount
when
that happens, as I recall.
Dima
![](https://secure.gravatar.com/avatar/56f108518d7ee2544412cc80978e3182.jpg?s=120&d=mm&r=g)
On 6/30/24 17:27, John wrote:
It is not clear what directory is the mount pount for this, but it is mounted read-only. No one, not even root, can write to it. Look at /etc/fstab
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
![](https://secure.gravatar.com/avatar/19e21a1f005c894a5543a086c1076e60.jpg?s=120&d=mm&r=g)
At Mon, 1 Jul 2024 12:45:11 -0700 Mark Sapiro <mark@msapiro.net> wrote:
If there was some sort of error, the file system would automatically be re-mounted read-only. Something like a power glitch, etc. can do this. Also a failing disk (sudden bad sector reads or writes).
-- Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364 Deepwoods Software -- Custom Software Services http://www.deepsoft.com/ -- Linux Administration Services heller@deepsoft.com -- Webhosting Services
![](https://secure.gravatar.com/avatar/1351fb866e8d35cad87c69e8b4c378bd.jpg?s=120&d=mm&r=g)
Yes a disk "failure" is possible,
I recently had a Samsung 980 pro nvme drive runout of spare blocks (due to bad firmware), this made the file system readonly.
Run smartctl on the disk(s) to check.
regards
Steven
From: Robert Heller <heller@deepsoft.com> Sent: Tuesday, 2 July 2024 8:21 am To: Mark Sapiro <mark@msapiro.net> Cc: mailman-users@python.org <mailman-users@python.org> Subject: [Mailman-Users] Re: Read-only file system
At Mon, 1 Jul 2024 12:45:11 -0700 Mark Sapiro <mark@msapiro.net> wrote:
If there was some sort of error, the file system would automatically be re-mounted read-only. Something like a power glitch, etc. can do this. Also a failing disk (sudden bad sector reads or writes).
-- Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364 Deepwoods Software -- Custom Software Services https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.deepsoft.com%2F&data=05%7C02%7Csteven.jones%40vuw.ac.nz%7C854ca3d22ee94fee6d9808dc9a0cd701%7Ccfe63e236951427e8683bb84dcf1d20c%7C0%7C0%7C638554627167864182%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=qm4l7rMm9RxwLTB%2FT%2FtTqj7Iswnbn4nIiPsm5pqRCnY%3D&reserved=0<http://www.deepsoft.com/> -- Linux Administration Services heller@deepsoft.com -- Webhosting Services
participants (6)
-
Carl Zwanzig
-
Dmitri Maziuk
-
John
-
Mark Sapiro
-
Robert Heller
-
Steven Jones