Command to Search for Filenames Exceeding 143 Characters?Output exceeding terminal window heightHow to batch clean filenames containing invalid charactersSearch/grep ftp remote filenamesMake grep work for special filenamesIs it correct to use certain special characters when naming filenames in Linux?List of filenames as argument for mplayer => mplayer doesn't recognize the filenamesCharacters best avoided in filenames when used in Bash, e.g. `?`Search for bash commandlinux find command for filenames without extension for unknown extensions

How to cut a perfect shape out of 4cm oak?

Is it really better for the environment if I take the stairs as opposed to a lift?

When applying for a visa has there ever been a case of embassy asking for proof of right to be in the present country?

How can I seal 8 inch round holes in my siding?

What plausible reasons why people forget they didn't originally live on this new planet?

Tear in RFs, not losing air

Should I respond to a sabotage accusation e-mail at work?

Who inspired the character Geordi La Forge?

Minimum number of turns to capture all pieces in Checkers

Confused about the meaning of the word "open" in this sentence

How would a race of humanoids with tails design [vehicle] seats?

I'm half of a hundred

Why it is a big deal whether or not Adam Schiff talked to the whistleblower?

Raise Error Concatenation in SQL Server

Does code obfuscation give any measurable security benefit?

How were Kurds involved (or not) in the invasion of Normandy?

Moving through the space of an invisible enemy creature in combat

Why is lambda return type not checked at compile time

Linux Commands in Python

Are my triangles similar?

How to pronounce correctly [b] and [p]? As well [t]/[d] and [k]/[g]

prevent single quotes in bash script

How can a stock trade for a fraction of a cent?

Why do baby boomers have to sell 5% of their retirement accounts by the end of the year?



Command to Search for Filenames Exceeding 143 Characters?


Output exceeding terminal window heightHow to batch clean filenames containing invalid charactersSearch/grep ftp remote filenamesMake grep work for special filenamesIs it correct to use certain special characters when naming filenames in Linux?List of filenames as argument for mplayer => mplayer doesn't recognize the filenamesCharacters best avoided in filenames when used in Bash, e.g. `?`Search for bash commandlinux find command for filenames without extension for unknown extensions






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;









6

















So some background first: I am attempting to convert a non-encrypted shared folder into an encrypted one on my Synology NAS and am seeing this error:



Synology NAS Error



So I would like to locate the offending files so that I may rename them. I have come up with the following grep command: grep -rle '[^ ]143,' * but it outputs all files with paths greater than 143 characters:



#recycle/Music/TO SORT/music/H/Hooligans----Heroes of Hifi/Metalcore Promotions - Heroes of Hifi - 03 Sly Like a Megan Fox.mp3
...


What I would like is for grep to split on / and then perform its search. Any idea on an efficient command to go about this (directory easily contains hundreds of thousands of files)?










share|improve this question




























  • For a collection of CJK p classes, see this stack overflow answer: stackoverflow.com/a/48673340

    – Andrew Domaszek
    May 26 at 3:23

















6

















So some background first: I am attempting to convert a non-encrypted shared folder into an encrypted one on my Synology NAS and am seeing this error:



Synology NAS Error



So I would like to locate the offending files so that I may rename them. I have come up with the following grep command: grep -rle '[^ ]143,' * but it outputs all files with paths greater than 143 characters:



#recycle/Music/TO SORT/music/H/Hooligans----Heroes of Hifi/Metalcore Promotions - Heroes of Hifi - 03 Sly Like a Megan Fox.mp3
...


What I would like is for grep to split on / and then perform its search. Any idea on an efficient command to go about this (directory easily contains hundreds of thousands of files)?










share|improve this question




























  • For a collection of CJK p classes, see this stack overflow answer: stackoverflow.com/a/48673340

    – Andrew Domaszek
    May 26 at 3:23













6












6








6


3






So some background first: I am attempting to convert a non-encrypted shared folder into an encrypted one on my Synology NAS and am seeing this error:



Synology NAS Error



So I would like to locate the offending files so that I may rename them. I have come up with the following grep command: grep -rle '[^ ]143,' * but it outputs all files with paths greater than 143 characters:



#recycle/Music/TO SORT/music/H/Hooligans----Heroes of Hifi/Metalcore Promotions - Heroes of Hifi - 03 Sly Like a Megan Fox.mp3
...


What I would like is for grep to split on / and then perform its search. Any idea on an efficient command to go about this (directory easily contains hundreds of thousands of files)?










share|improve this question

















So some background first: I am attempting to convert a non-encrypted shared folder into an encrypted one on my Synology NAS and am seeing this error:



Synology NAS Error



So I would like to locate the offending files so that I may rename them. I have come up with the following grep command: grep -rle '[^ ]143,' * but it outputs all files with paths greater than 143 characters:



#recycle/Music/TO SORT/music/H/Hooligans----Heroes of Hifi/Metalcore Promotions - Heroes of Hifi - 03 Sly Like a Megan Fox.mp3
...


What I would like is for grep to split on / and then perform its search. Any idea on an efficient command to go about this (directory easily contains hundreds of thousands of files)?







command-line filenames synology






share|improve this question
















share|improve this question













share|improve this question




share|improve this question








edited Jun 21 at 20:04









Jeff Schaller

50.3k11 gold badges74 silver badges167 bronze badges




50.3k11 gold badges74 silver badges167 bronze badges










asked May 26 at 1:47









StunnerStunner

1336 bronze badges




1336 bronze badges















  • For a collection of CJK p classes, see this stack overflow answer: stackoverflow.com/a/48673340

    – Andrew Domaszek
    May 26 at 3:23

















  • For a collection of CJK p classes, see this stack overflow answer: stackoverflow.com/a/48673340

    – Andrew Domaszek
    May 26 at 3:23
















For a collection of CJK p classes, see this stack overflow answer: stackoverflow.com/a/48673340

– Andrew Domaszek
May 26 at 3:23





For a collection of CJK p classes, see this stack overflow answer: stackoverflow.com/a/48673340

– Andrew Domaszek
May 26 at 3:23










3 Answers
3






active

oldest

votes


















8


















Try:



find /your/path | grep -E '[^/]143,$'





share|improve this answer

































    11


















    Although the GNU ‘findutils-default’ regular expression syntax doesn't provide a n,m interval quantifier, you can use a -regex test in GNU find if you select a different regextype, for example:



    find . -regextype posix-extended -regex '.*/[^/]143,$'


    or



    find . -regextype egrep -regex '.*/[^/]143,$'


    or



    find . -regextype posix-basic -regex '.*/[^/]143,$'


    etc. There may be other regextypes that support n,m intervals, either with or without escaping.



    Compared to piping the results of find to a separate grep command, this will match across newlines (i.e. the find regex flavors differ from their namesakes in that . matches the newline character by default).






    share|improve this answer



































      5


















      If you've already got a locate db, it is very fast at this.



      locate --regex '.*/[^/]143,$'





      share|improve this answer



























        Your Answer








        StackExchange.ready(function()
        var channelOptions =
        tags: "".split(" "),
        id: "106"
        ;
        initTagRenderer("".split(" "), "".split(" "), channelOptions);

        StackExchange.using("externalEditor", function()
        // Have to fire editor after snippets, if snippets enabled
        if (StackExchange.settings.snippets.snippetsEnabled)
        StackExchange.using("snippets", function()
        createEditor();
        );

        else
        createEditor();

        );

        function createEditor()
        StackExchange.prepareEditor(
        heartbeatType: 'answer',
        autoActivateHeartbeat: false,
        convertImagesToLinks: false,
        noModals: true,
        showLowRepImageUploadWarning: true,
        reputationToPostImages: null,
        bindNavPrevention: true,
        postfix: "",
        imageUploader:
        brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
        contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/4.0/"u003ecc by-sa 4.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
        allowUrls: true
        ,
        onDemand: true,
        discardSelector: ".discard-answer"
        ,immediatelyShowMarkdownHelp:true
        );



        );














        draft saved

        draft discarded
















        StackExchange.ready(
        function ()
        StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f521096%2fcommand-to-search-for-filenames-exceeding-143-characters%23new-answer', 'question_page');

        );

        Post as a guest















        Required, but never shown


























        3 Answers
        3






        active

        oldest

        votes








        3 Answers
        3






        active

        oldest

        votes









        active

        oldest

        votes






        active

        oldest

        votes









        8


















        Try:



        find /your/path | grep -E '[^/]143,$'





        share|improve this answer






























          8


















          Try:



          find /your/path | grep -E '[^/]143,$'





          share|improve this answer




























            8














            8










            8









            Try:



            find /your/path | grep -E '[^/]143,$'





            share|improve this answer














            Try:



            find /your/path | grep -E '[^/]143,$'






            share|improve this answer













            share|improve this answer




            share|improve this answer










            answered May 26 at 2:09









            Jim L.Jim L.

            2,3781 gold badge4 silver badges12 bronze badges




            2,3781 gold badge4 silver badges12 bronze badges


























                11


















                Although the GNU ‘findutils-default’ regular expression syntax doesn't provide a n,m interval quantifier, you can use a -regex test in GNU find if you select a different regextype, for example:



                find . -regextype posix-extended -regex '.*/[^/]143,$'


                or



                find . -regextype egrep -regex '.*/[^/]143,$'


                or



                find . -regextype posix-basic -regex '.*/[^/]143,$'


                etc. There may be other regextypes that support n,m intervals, either with or without escaping.



                Compared to piping the results of find to a separate grep command, this will match across newlines (i.e. the find regex flavors differ from their namesakes in that . matches the newline character by default).






                share|improve this answer
































                  11


















                  Although the GNU ‘findutils-default’ regular expression syntax doesn't provide a n,m interval quantifier, you can use a -regex test in GNU find if you select a different regextype, for example:



                  find . -regextype posix-extended -regex '.*/[^/]143,$'


                  or



                  find . -regextype egrep -regex '.*/[^/]143,$'


                  or



                  find . -regextype posix-basic -regex '.*/[^/]143,$'


                  etc. There may be other regextypes that support n,m intervals, either with or without escaping.



                  Compared to piping the results of find to a separate grep command, this will match across newlines (i.e. the find regex flavors differ from their namesakes in that . matches the newline character by default).






                  share|improve this answer






























                    11














                    11










                    11









                    Although the GNU ‘findutils-default’ regular expression syntax doesn't provide a n,m interval quantifier, you can use a -regex test in GNU find if you select a different regextype, for example:



                    find . -regextype posix-extended -regex '.*/[^/]143,$'


                    or



                    find . -regextype egrep -regex '.*/[^/]143,$'


                    or



                    find . -regextype posix-basic -regex '.*/[^/]143,$'


                    etc. There may be other regextypes that support n,m intervals, either with or without escaping.



                    Compared to piping the results of find to a separate grep command, this will match across newlines (i.e. the find regex flavors differ from their namesakes in that . matches the newline character by default).






                    share|improve this answer
















                    Although the GNU ‘findutils-default’ regular expression syntax doesn't provide a n,m interval quantifier, you can use a -regex test in GNU find if you select a different regextype, for example:



                    find . -regextype posix-extended -regex '.*/[^/]143,$'


                    or



                    find . -regextype egrep -regex '.*/[^/]143,$'


                    or



                    find . -regextype posix-basic -regex '.*/[^/]143,$'


                    etc. There may be other regextypes that support n,m intervals, either with or without escaping.



                    Compared to piping the results of find to a separate grep command, this will match across newlines (i.e. the find regex flavors differ from their namesakes in that . matches the newline character by default).







                    share|improve this answer















                    share|improve this answer




                    share|improve this answer








                    edited May 26 at 21:42

























                    answered May 26 at 2:41









                    steeldriversteeldriver

                    44.3k6 gold badges58 silver badges98 bronze badges




                    44.3k6 gold badges58 silver badges98 bronze badges
























                        5


















                        If you've already got a locate db, it is very fast at this.



                        locate --regex '.*/[^/]143,$'





                        share|improve this answer






























                          5


















                          If you've already got a locate db, it is very fast at this.



                          locate --regex '.*/[^/]143,$'





                          share|improve this answer




























                            5














                            5










                            5









                            If you've already got a locate db, it is very fast at this.



                            locate --regex '.*/[^/]143,$'





                            share|improve this answer














                            If you've already got a locate db, it is very fast at this.



                            locate --regex '.*/[^/]143,$'






                            share|improve this answer













                            share|improve this answer




                            share|improve this answer










                            answered May 26 at 3:16









                            Andrew DomaszekAndrew Domaszek

                            2301 silver badge5 bronze badges




                            2301 silver badge5 bronze badges































                                draft saved

                                draft discarded















































                                Thanks for contributing an answer to Unix & Linux Stack Exchange!


                                • Please be sure to answer the question. Provide details and share your research!

                                But avoid


                                • Asking for help, clarification, or responding to other answers.

                                • Making statements based on opinion; back them up with references or personal experience.

                                To learn more, see our tips on writing great answers.




                                draft saved


                                draft discarded














                                StackExchange.ready(
                                function ()
                                StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f521096%2fcommand-to-search-for-filenames-exceeding-143-characters%23new-answer', 'question_page');

                                );

                                Post as a guest















                                Required, but never shown





















































                                Required, but never shown














                                Required, but never shown












                                Required, but never shown







                                Required, but never shown

































                                Required, but never shown














                                Required, but never shown












                                Required, but never shown







                                Required, but never shown









                                Popular posts from this blog

                                Tamil (spriik) Luke uk diar | Nawigatjuun

                                Align equal signs while including text over equalitiesAMS align: left aligned text/math plus multicolumn alignmentMultiple alignmentsAligning equations in multiple placesNumbering and aligning an equation with multiple columnsHow to align one equation with another multline equationUsing \ in environments inside the begintabularxNumber equations and preserving alignment of equal signsHow can I align equations to the left and to the right?Double equation alignment problem within align enviromentAligned within align: Why are they right-aligned?

                                Training a classifier when some of the features are unknownWhy does Gradient Boosting regression predict negative values when there are no negative y-values in my training set?How to improve an existing (trained) classifier?What is effect when I set up some self defined predisctor variables?Why Matlab neural network classification returns decimal values on prediction dataset?Fitting and transforming text data in training, testing, and validation setsHow to quantify the performance of the classifier (multi-class SVM) using the test data?How do I control for some patients providing multiple samples in my training data?Training and Test setTraining a convolutional neural network for image denoising in MatlabShouldn't an autoencoder with #(neurons in hidden layer) = #(neurons in input layer) be “perfect”?