Hi,
I made a mistake in the last email: it broke because our NFS server went
down, not because of the "can't read superblock" error.
I talked to our admins and they said that this morning the NFS servers
crashed and came back up. So I suspect that something about the NFS
server bounce fixed the superblock problem.
So to recap what happened:
1. Definitely worked on Friday
2. Started showing symptoms over the weekend but I didn't check the logs.
3. apt-get dist-upgrade on Monday, after which I checked the logs and
found the "can't read superblock" error. I tried downgrading a few
packages but it didn't go away. (It worked fine from another Debian
machine.)
4. NFS server crash on Tuesday morning.
5. Works fine late Tuesday morning after NFS servers are back up.
6. NFS server crash early Tuesday afternoon, mistakenly reported as an
instance of this problem.
Thanks,
Stefanie
Debian Bug Tracking System wrote:
Thank you for the additional information you have supplied regarding
this problem report. It has been forwarded to the package maintainer(s)
and to other interested parties to accompany the original report.
Your message has been sent to the package maintainer(s):
LaMont Jones <[EMAIL PROTECTED]>
If you wish to continue to submit further information on your problem,
please send it to [EMAIL PROTECTED], as before.
Please do not reply to the address at the top of this message,
unless you wish to report a problem with the Bug-tracking system.
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
