download.opensuse.org cannot be accessed
#3 Updated by email@example.com 5 months 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
You can closed this ticket.
On Wed, Sep 25, 2019 at 8:03 PM firstname.lastname@example.org wrote:
Issue #57359 has been updated by mcaj.
Status changed from New to Feedback
Assignee set to mcaj
Priority changed from Normal to Immediate
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.
tickets #57359: download.opensuse.org cannot be accessed
- Author: email@example.com
- Status: Feedback
- Priority: Immediate
- Assignee: mcaj
* Target version:¶
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?
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
- 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?