我买了两个。其中一个挂了10天了,官方正在fsck……
Jan 16 10:23PM: It's doing /lib on CT249 now
Jan 14 9:40PM: It's doing /var on CT713 now. When we report here on what it's doing, it's simply a report on what it's doing at the time, it does not mean that it's only been running fsck on 1-2 VPS for the few hours since last report.
FSCK runs will run as long as is needed to repair and check the filesystem, so with the large arrays are on a system, and how long ago the previous FSCK was done, and how much data did change. Really no way to tell you this. And fsck was never ran on tamil, not even once since it was first setup about a year ago in March 2016.
Jan 14 6:27PM: Checking /var on CT745 now
Jan 13 1:52PM: Checking /var on CT388 now
Jan 12 8:45AM: Checking /usr on CT513 now
Jan 11 9:19PM: It's running fsck on CT806 /var now
Jan 11 6:32AM: Since it is still recovering and doing the check disk, we can't replace the server yet. Plus all latest backup is inside the server so we can't really get them without taking this down.
Jan 11 5:59AM: It's doing /var on CT243 now
Jan 10 7:53PM: It's doing /var on CT803 now
Jan 10 7:35AM: It's doing /var on CT660 now
Jan 10 5:37AM: It's doing /var on CT175 now
Jan 9 7:14PM: Checking /var on CT630 now
Jan 9 8:45AM: It's currently checking /var on CT233 now
Jan 9 3:00AM: It's checking /var on CT263 now
Jan 8 6:16PM: Check disk is still running, now checking /usr on CT140.
Jan 8 5:23AM: Check disk is still running now, we'll update here when it is done. We cannot do anything until it is done.
Jan 7 7:43PM: Check disk is still checking/fixing VPS data one account at a time. We are not sure how long it will be done. We hope in less than 6 hours, 12 the most.
Jan 7 4:28PM: Check disk is still running now, we'll update here when it is done.
Jan 7 11:13AM: Check disk is still running now, should be up when it is done.
Jan 7 10:46AM: Check disk is still running now, should be up when it is done.
Jan 7 9:43AM: Check disk is still running now, should be up when it is done.t
Jan 7 8:51AM: A VPS CT653 found to be abusing the resources on tamil node so it's running very slow and since we can't do anything inside the server locally, we're rebooting it now.
|