| To: | linux-xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: Fragmentation (was: XFS NFS server Oops) |
| From: | Jason White <jasonw@xxxxxxxxxxxxxxxxxxxxxxxx> |
| Date: | Wed, 20 Mar 2002 14:26:48 +1100 |
| In-reply-to: | <Pine.LNX.4.44.0203200925430.8497-100000@gusi.leathercollection.ph> |
| References: | <1016578034.28166.25.camel@jen.americas.sgi.com> <Pine.LNX.4.44.0203200925430.8497-100000@gusi.leathercollection.ph> |
| Reply-to: | jasonw@xxxxxxxxxxxxxxxxxxxxxxxx |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
While on the subject of xfs_fsr, it would also be of interest to know what risks are involved in running it. For example, what damage can be caused if the system crashes while files are being defragmented, and is there likely to be data loss if the system is cleanly shut down while xfs_fsr is running? Also, xfs_fsr needs to avoid certain files, especially kernel images, the location of which on the disk is significant to the boot process if I understand correctly. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Fragmentation (was: XFS NFS server Oops), Federico Sevilla III |
|---|---|
| Next by Date: | Re: Fragmentation (was: XFS NFS server Oops), Rupa Schomaker |
| Previous by Thread: | Fragmentation (was: XFS NFS server Oops), Federico Sevilla III |
| Next by Thread: | Re: Fragmentation (was: XFS NFS server Oops), Rupa Schomaker |
| Indexes: | [Date] [Thread] [Top] [All Lists] |