| To: | Supratik Goswami <supratiksekhar@xxxxxxxxx> |
|---|---|
| Subject: | Re: File system remain unresponsive until the system is rebooted. |
| From: | Dave Chinner <david@xxxxxxxxxxxxx> |
| Date: | Tue, 31 Jan 2012 12:31:24 +1100 |
| Cc: | xfs@xxxxxxxxxxx |
| In-reply-to: | <CANs4eSBWLc4HxAbPZ8kOVOdJ7RKiA+-ai3Q2J+FAyuzHtUqfdg@xxxxxxxxxxxxxx> |
| References: | <CANs4eSBWLc4HxAbPZ8kOVOdJ7RKiA+-ai3Q2J+FAyuzHtUqfdg@xxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
On Mon, Jan 30, 2012 at 02:48:58PM +0530, Supratik Goswami wrote: > Hi > > We are using RAID-0 volumes as PV's in our LVM stack and XFS as the > filesystem. > > The kernel logged the below call trace when the filesystem was being > expanded using "xfs_growfs" command. > We have used xfs_grofs at least 3 times earlier but did not cam across > this situation. > > The files system remained unresponsive until we rebooted the system > and again increased the size of the filesystem. > This time it worked fine. Can you please tell us why xfs_grofs hanged > suddenly ? What kernel? Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: xfs task blocked for more than 120 seconds, Sami Liedes |
|---|---|
| Next by Date: | Re: Performance problem - reads slower than writes, Dave Chinner |
| Previous by Thread: | Re: File system remain unresponsive until the system is rebooted., Peter Grandi |
| Next by Thread: | Re: File system remain unresponsive until the system is rebooted., Supratik Goswami |
| Indexes: | [Date] [Thread] [Top] [All Lists] |