Reputation
430
Top tag
Next privilege 500 Rep.
Access review queues
Badges
7 18
Impact
~27k people reached

Apr
28
awarded  Notable Question
Mar
16
awarded  Nice Question
Feb
11
comment raid0 (soft-RAID using Linux md drivers) hosting XFS: how to repair after replacing bad disk?
I have posited (but not confirmed) that the a side effect of this situation (any attempts to write to the ports of the filesystem on md0 which exist on sda) is for the FS driver to treat those as "bad blocks." This is the essence of my question. Is it possible to "repair" the filesystem such that the data across the other X-1 disks in this array does not have to be moved around?
Feb
11
comment raid0 (soft-RAID using Linux md drivers) hosting XFS: how to repair after replacing bad disk?
md0 is a raid0 of sda sdb ... sdx; there is a filesystem (in this case XFS) on md0. one of the disks (sda) dies. The rest of the filesystem is still there, alive, active, the OS continues to allow access to it; most of the processes accessing data on the filesystem are unaffected. Only those which access portions of the filesystem that reside on sda see I/O errors (unless a critical portion of the FS is affected and causes a kernel panic or read-only remount --- which I'm not seeing in my real-work exemplar ... a system which is in this state even as I'm typing this).
Feb
11
asked Does OpenStack (Nova) Support VM migration of LOCAL virtual disk images (not just Cinder)?
Feb
10
comment raid0 (soft-RAID using Linux md drivers) hosting XFS: how to repair after replacing bad disk?
The OS (Linux) won't "fail" the block device driver will return I/O errors. The filesystem driver will (presumably) mark those blocks as "bad" and the OS will return I/O errors to any user space processes (or kernel threads?) which have made system calls attempting to read data from the filesystem blocks serviced by that (physical device). As I've said, I know that any VMs or other processes which data on the affected portions of the OS will die (or at least have to handle their own I/O errors). I'm asking if there's a way to repair to FS so that the "bad" regions are reclaimed.
Feb
10
comment raid0 (soft-RAID using Linux md drivers) hosting XFS: how to repair after replacing bad disk?
(The alternative, if there's no way to forced XFS to re-evaluate the "bad blocks" is to forced all my OpenStack customers to "drain" their VMs off that host so I can do a new mkfs on the md0 device).
Feb
10
comment raid0 (soft-RAID using Linux md drivers) hosting XFS: how to repair after replacing bad disk?
I'm well aware that raid0 is no redundancy. In this case any VMs whose data was hosted on blocks affected by the drive failure have already died and been re-spawned by the customers. So the question concerns how to restore the FS capacity without impacting the VMs which were hosted on other portions of the FS. --- think "linear mode" RAID0 rather than interleaved.
Feb
10
asked raid0 (soft-RAID using Linux md drivers) hosting XFS: how to repair after replacing bad disk?
Feb
10
comment mdadm did not notice a failed disk in raid0
The most common use-cases for RAID0 are those wherein the data redundancy/replication is happening at the host level rather than the storage device level. In particular we have HDFS and Kafka where whole nodes can fail without impact to the service nor any concern about lost data (it's replicated on other nodes).
Nov
4
awarded  Popular Question
Sep
7
awarded  Constituent
Sep
2
awarded  Caucus
Jul
8
comment What are your best senior level Linux interview questions
gnp: fixed. Thank you.
Jul
8
revised What are your best senior level Linux interview questions
Fixed missing closing single (hard) quote in Perl `unlink` example; as per comment.
Jul
3
accepted How do I Delegate a subdomain to Route53
Jul
2
awarded  Popular Question
Mar
30
awarded  Announcer
Mar
19
awarded  Curious
Feb
4
comment How do I bind a key to a macro in GNU screen from the command line?
Is there an equivalent way to do this under tmux?