tickets #57359
closeddownload.opensuse.org cannot be accessed
Added by medwinz@gmail.com about 5 years ago. Updated about 5 years ago.
100%
Description
Hi Admin,
It is just a gentle report I cannot access download.opensuse.org from
my location in Indonesia 25 Sept 2019, around 7:40 PM
I checked on https://status.opensuse.org/ and it said major outage
Is there any maintenance going on?
Kind regards,¶
Edwin
Updated by mcaj about 5 years ago
- Status changed from New to Feedback
- Assignee set to mcaj
- Priority changed from Normal to Immediate
HI,
There was a problem with file system.
The machine is now up but we are still checking what happen.
Please check it from outside of world to access it.
Martin
Updated by medwinz@gmail.com about 5 years ago
Hi Martin / Admin,
It is a very quick response, thanks!
Yes it is up again and I can access it. I'm still on this earth, and I
can report it that it is accessible :-)
I maintain Indonesian mirror repository, https://repo.opensuse.id so I
got many questions about this outage. Once again thank you for the
hard work.
You can closed this ticket.
Kind regards,¶
Edwin
On Wed, Sep 25, 2019 at 8:03 PM admin@opensuse.org wrote:
[openSUSE Tracker]
Issue #57359 has been updated by mcaj.Status changed from New to Feedback
Assignee set to mcaj
Priority changed from Normal to ImmediateHI,
There was a problem with file system.
The machine is now up but we are still checking what happen.Please check it from outside of world to access it.
Martin
tickets #57359: download.opensuse.org cannot be accessed
https://progress.opensuse.org/issues/57359#change-246152
- Author: medwinz@gmail.com
- Status: Feedback
- Priority: Immediate
- Assignee: mcaj
- Category:
* Target version:¶
Hi Admin,
It is just a gentle report I cannot access download.opensuse.org from
my location in Indonesia 25 Sept 2019, around 7:40 PMI checked on https://status.opensuse.org/ and it said major outage
Is there any maintenance going on?
Kind regards,¶
Edwin
--
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://progress.opensuse.org/my/account
Updated by pjessen about 5 years ago
It's still very full -
/dev/vdb 209663872 205131840 4532032 98% /var/log
/dev/mapper/pontifex3-pontifex3 18064193536 18002576384 61617152 100% /srv
I deleted some old (2016) log from /srv/bs, but it was only a few gigabytes.
Updated by medwin about 5 years ago
Knurpht wrote:
And the same thing is going on again.
Yes, I confirm it happens again.
If pjessen mention in #5 is true, then more space is needed.
Updated by pjessen about 5 years ago
- Status changed from Feedback to In Progress
Yes, same thing -
[42241.721656] XFS (dm-0): Internal error xfs_trans_cancel at line 1005 of file ../fs/xfs/xfs_trans.c. Caller xfs_create+0x419/0x680 [xfs]
[42241.721815] CPU: 1 PID: 27254 Comm: rsyncd Not tainted 4.12.14-lp151.28.13-default #1 openSUSE Leap 15.1
[42241.721817] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.0.0-prebuilt.qemu-project.org 04/01/2014
[42241.721819] Call Trace:
[42241.721850] dump_stack+0x5c/0x86
[42241.721925] xfs_trans_cancel+0xad/0xd0 [xfs]
[42241.722184] xfs_create+0x419/0x680 [xfs]
[42241.722276] xfs_generic_create+0x1e1/0x2c0 [xfs]
[42241.722286] vfs_mkdir+0x101/0x1b0
[42241.722290] SyS_mkdir+0xcf/0xf0
[42241.722296] do_syscall_64+0x7b/0x160
[42241.722303] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[42241.722308] RIP: 0033:0x7f177e5f48d7
[42241.722310] RSP: 002b:00007ffeeadd6dc8 EFLAGS: 00000206 ORIG_RAX: 0000000000000053
[42241.722315] RAX: ffffffffffffffda RBX: 0000559de02c9a90 RCX: 00007f177e5f48d7
[42241.722317] RDX: c0fe880000000000 RSI: 00000000000001c0 RDI: 00007ffeeadd9100
[42241.722319] RBP: 00000000ffffffff R08: 0000000000008800 R09: 0000000000000000
[42241.722321] R10: 0000000000000002 R11: 0000000000000206 R12: 0000000000000000
[42241.722323] R13: 0000000000000000 R14: 00000000ffffffff R15: 00007ffeeadd9100
[42241.722329] XFS (dm-0): xfs_do_force_shutdown(0x8) called from line 1006 of file ../fs/xfs/xfs_trans.c. Return address = 0xffffffffa0597b16
[42241.747390] XFS (dm-0): Corruption of in-memory data detected. Shutting down filesystem
[42241.747394] XFS (dm-0): Please umount the filesystem and rectify the problem(s)
[42241.757116] XFS (dm-0): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5.
[42241.760046] XFS (dm-0): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5.
[42241.965963] XFS (dm-0): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5.
Martin, did you reboot it yesterday?
Updated by pjessen about 5 years ago
To those who are following this issue - Martin is looking at it, and he will be adding some more space later this morning.
Updated by bmwiedemann about 5 years ago
looks much better now:
> df -m /var/log/ /srv/
Filesystem 1M-blocks Used Available Use% Mounted on
/dev/vdb 204750 99558 105193 49% /var/log
/dev/mapper/pontifex3-pontifex3 19737966 17641900 2096067 90% /srv