Goffredo Baroncelli posted on Mon, 20 Oct 2014 22:21:04 +0200 as excerpted: > On 10/20/2014 07:37 PM, Robert White wrote: >> On 10/18/2014 04:41 PM, Russell Coker wrote: > [...] >> Also you said that you are using a 32bit user space "copied from >> another server" under a 64bit kernel. Is the "ls" command a 32 bit >> executable then? > > Could this be related to the inode overflow in 32 bit system (see > inode_cache options) ? If so running a 64bit "ls -i" should work.... Good point. Russell might just owe you a beverage of choice. =:^) The inode_cache mount option isn't recommended for any bitness. @ Russ, are you mounting with inode_cache? If so, definitely try running without it and see if it changes the results. (FWIW I wish that mount option would just go away as it would definitely remove an invitation to a Russian roulette party with their data for the unwary, but I suppose there's someone paying some bills somewhere that wants it kept for some specific use-case where the performance gain must be worth the calculated risk, thus continuing that invitation to data Russian roulette for everyone else.) -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
