search for: srwt

...delete these "weird files" (the term used by the operating system utilities). Here are a few examples. The original files were created on Windoze 98 version 2 circa 2001. > 2411957 p--x---rwx 65487 299196551 2101198676 775118685 Apr 5 1943 00002434.thm > 2411959 ?--xr-srwT 6581 42211 24637 1333254828 Jan 30 2029 00002435 > 2411960 -rwxr-xr-x 44608 305922048 3679253821 14580319157523353423 Dec 1 1949 00002437 lsattr: Operation not supported While reading flags on ..... stat ....... A "normal" file looks this this example: &gt...

...ound with bogus inodes, for example: br--r--r-- 1 62334 16197 237, 37 May 6 1995 #526307 s-wx-----x 1 65257 255 2530964044 Oct 6 1916 #526309 prwsrwxrw- 1 51879 13066 0 Apr 21 1939 #526318 srwsr--r-x 1 58596 10074 3732091634 May 28 1961 #526323 p-w---Srwt 1 44798 2118 0 Sep 3 2024 #526326 I think these were created after my *gak* Windows 98 partition did something horrible. Or maybe fsck was trying to recover from whatever Win98 did. In any event, rm, chmod, unlink(2) all give "operation not permitted", even though I...

...e attributes are never applied to the destination. To see the current behavior, run: mkdir -p a/b chmod 3756 a # Notice that this wacky mode appears in the listing # even though the receiver doesn't apply it. rsync -a -R --no-implied-dirs --list-only a/b The result: drwxr-srwT 72 2007/09/22 20:24:55 a drwx------ 48 2007/09/22 20:24:55 a/b -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

An EXT3 filesystem technically isn't supposed to require an fsck, correct? Well, as per my last email re: EXT3 Crash?! I ran an fsck on a couple of my LVMs. It said they were clean, but then I decided to be 100% sure and force an fsck. Error after Error after Error after Error. I wound up losing almost half the data on my LVM due to all the errors. What's the real deal? Am I doing