| To: | linux-xfs@xxxxxxxxxxx |
|---|---|
| Subject: | data loss with delayed allocaton |
| From: | Fong Vang <sudoyang@xxxxxxxxx> |
| Date: | Thu, 26 Jan 2006 10:25:31 -0800 |
| Domainkey-signature: | a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=dVpm9r6bASOIacgaTTBn055JiTrA/kW5ir0szQd9UEpEDSyv/YCjHWtfEsnFL/jIyOG5RTHa5uFxjV05oJZeERG1aaPYAAPvcYh88gLDrwdz1iNLdu24Wd7sSZN6zK+9ZV8Va95G/u/fOGw5hbo9mjSbjkB7GeBqi7DnDXhhU9A= |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
I just read the following article: http://madpenguin.org/cms/index.php/?m=show&opt=printable&id=6045 Near the end, this line caught my attention: "the delay means that while a crash will not destroy FS, it might result in significant loss of data that has not yet been written to the disc." I'm just wondering if this delay parameter is tunable and what the default is. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: moving disconnected inodes to lost+found, Eric Sandeen |
|---|---|
| Next by Date: | Re: data loss with delayed allocaton, Eric Sandeen |
| Previous by Thread: | moving disconnected inodes to lost+found, Seungsu Yi |
| Next by Thread: | Re: data loss with delayed allocaton, Eric Sandeen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |